From: Christoph Hellwig <hch@lst•de>
To: Mingbao Sun <sunmingbao@tom•com>
Cc: Christoph Hellwig <hch@lst•de>,
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 16:05:06 +0100 [thread overview]
Message-ID: <20220310150506.GA1939@lst.de> (raw)
In-Reply-To: <20220310230300.00004612@tom.com>
On Thu, Mar 10, 2022 at 11:03:00PM +0800, Mingbao Sun wrote:
> 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?
I think for the initial RFC either is fine, just clearly state which.
> 2. what's the recipients for this series of patches?
> netdev or nvme or both?
both.
next prev parent reply other threads:[~2022-03-10 15:10 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
2022-03-10 15:05 ` Christoph Hellwig [this message]
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=20220310150506.GA1939@lst.de \
--to=hch@lst$(echo .)de \
--cc=ao.sun@dell$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--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=sunmingbao@tom$(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