netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Sitnicki <jakub@cloudflare.com>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, eparis@parisplace.org,
	kernel-team@cloudflare.com, kuba@kernel.org,
	marek@cloudflare.com, ncardwell@google.com,
	netdev@vger.kernel.org, pabeni@redhat.com, paul@paul-moore.com,
	selinux@vger.kernel.org, stephen.smalley.work@gmail.com
Subject: Re: [PATCH net-next v4 1/2] inet: Add IP_LOCAL_PORT_RANGE socket option
Date: Mon, 23 Jan 2023 21:46:45 +0100	[thread overview]
Message-ID: <87zga9vuyr.fsf@cloudflare.com> (raw)
In-Reply-To: <20230123175526.59356-1-kuniyu@amazon.com>

On Mon, Jan 23, 2023 at 09:55 AM -08, Kuniyuki Iwashima wrote:

[...]

>
> Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
>
> In case you might forgot this comment, but the patch looks good to me.
> https://lore.kernel.org/netdev/20230111005923.47037-1-kuniyu@amazon.com/

Sorry, it has slipped my mind. I'll apply it in v5.

Thank you for reviewing.

  reply	other threads:[~2023-01-23 20:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 14:44 [PATCH net-next v4 0/2] Add IP_LOCAL_PORT_RANGE socket option Jakub Sitnicki
2023-01-23 14:44 ` [PATCH net-next v4 1/2] inet: " Jakub Sitnicki
2023-01-23 17:47   ` Leon Romanovsky
2023-01-23 20:48     ` Jakub Sitnicki
2023-01-24  3:35       ` Jakub Kicinski
2023-01-23 17:55   ` Kuniyuki Iwashima
2023-01-23 20:46     ` Jakub Sitnicki [this message]
2023-01-23 14:44 ` [PATCH net-next v4 2/2] selftests/net: Cover the " Jakub Sitnicki
2023-01-23 17:58   ` Kuniyuki Iwashima

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=87zga9vuyr.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=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).