public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mingbao Sun <sunmingbao@tom•com>
To: Christoph Hellwig <hch@lst•de>
Cc: Eric Dumazet <edumazet@google•com>,
	"David S . Miller" <davem@davemloft•net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6•org>,
	David Ahern <dsahern@kernel•org>,
	Jakub Kicinski <kuba@kernel•org>,
	netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
	tyler.sun@dell•com, ping.gan@dell•com, yanxiu.cai@dell•com,
	libin.zhang@dell•com, ao.sun@dell•com
Subject: Re: [PATCH] tcp: export symbol tcp_set_congestion_control
Date: Thu, 10 Mar 2022 23:03:00 +0800	[thread overview]
Message-ID: <20220310230300.00004612@tom.com> (raw)
In-Reply-To: <20220310141135.GA750@lst.de>

On Thu, 10 Mar 2022 15:11:35 +0100
Christoph Hellwig <hch@lst•de> wrote:

> Please submit this together with the actual user(s) in a series.
> Patches to just export random symbols are a no-go.

Got it.
many thanks for informing.

BTW:
could you give me the answer to the following questions?
1. Against which repo should I prepare and test this series of patches?
   netdev or nvme?

2. what's the recipients for this series of patches?
   netdev or nvme or both?

  reply	other threads:[~2022-03-10 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 13:48 [PATCH] tcp: export symbol tcp_set_congestion_control Mingbao Sun
2022-03-10 14:11 ` Christoph Hellwig
2022-03-10 15:03   ` Mingbao Sun [this message]
2022-03-10 15:05     ` Christoph Hellwig
2022-03-10 20:48 ` Jakub Kicinski
2022-03-11  1:29   ` Mingbao Sun
2022-03-11  7:19   ` Christoph Hellwig
2022-03-11 16:18     ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220310230300.00004612@tom.com \
    --to=sunmingbao@tom$(echo .)com \
    --cc=ao.sun@dell$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dsahern@kernel$(echo .)org \
    --cc=edumazet@google$(echo .)com \
    --cc=hch@lst$(echo .)de \
    --cc=kuba@kernel$(echo .)org \
    --cc=libin.zhang@dell$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=ping.gan@dell$(echo .)com \
    --cc=tyler.sun@dell$(echo .)com \
    --cc=yanxiu.cai@dell$(echo .)com \
    --cc=yoshfuji@linux-ipv6$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox