From: Jakub Sitnicki <jakub@cloudflare.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Neal Cardwell <ncardwell@google.com>,
selinux@vger.kernel.org, Paul Moore <paul@paul-moore.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Eric Paris <eparis@parisplace.org>,
kernel-team@cloudflare.com,
Marek Majkowski <marek@cloudflare.com>
Subject: Re: [PATCH net-next v5 1/2] inet: Add IP_LOCAL_PORT_RANGE socket option
Date: Tue, 24 Jan 2023 14:32:38 +0100 [thread overview]
Message-ID: <878rhsvyyd.fsf@cloudflare.com> (raw)
In-Reply-To: <Y8/XYBtzMzKyIZjo@unreal>
On Tue, Jan 24, 2023 at 03:04 PM +02, Leon Romanovsky wrote:
> On Tue, Jan 24, 2023 at 01:33:07PM +0100, Jakub Sitnicki wrote:
[...]
>> I'm happy to adjust the changelog in whichever way that will make
>> everyone content. However, ATM we don't have one, it seems.
>
> We have, just some of us don't care. It doesn't mean they prefer to see
> changelog before ---.
OK. Thanks for clarifying. Will sent v6 with changelog moved.
next prev parent reply other threads:[~2023-01-24 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 10:05 [PATCH net-next v5 0/2] Add IP_LOCAL_PORT_RANGE socket option Jakub Sitnicki
2023-01-24 10:05 ` [PATCH net-next v5 1/2] inet: " Jakub Sitnicki
2023-01-24 12:23 ` Leon Romanovsky
2023-01-24 12:33 ` Jakub Sitnicki
2023-01-24 13:04 ` Leon Romanovsky
2023-01-24 13:32 ` Jakub Sitnicki [this message]
2023-01-24 10:05 ` [PATCH net-next v5 2/2] selftests/net: Cover the " Jakub Sitnicki
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=878rhsvyyd.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eparis@parisplace.org \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=leon@kernel.org \
--cc=marek@cloudflare.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).