From: Kuniyuki Iwashima <kuniyu@amazon.co.jp>
To: <davem@davemloft.net>
Cc: <benh@amazon.com>, <edumazet@google.com>, <kraig@google.com>,
<kuba@kernel.org>, <kuni1840@gmail.com>, <kuniyu@amazon.co.jp>,
<kuznet@ms2.inr.ac.ru>, <netdev@vger.kernel.org>,
<osa-contribution-log@amazon.com>, <pabeni@redhat.com>,
<willemb@google.com>, <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH net 0/2] udp: Fix reuseport selection with connected sockets.
Date: Wed, 22 Jul 2020 13:28:02 +0900 [thread overview]
Message-ID: <20200722042802.8724-1-kuniyu@amazon.co.jp> (raw)
In-Reply-To: <20200721.153239.840568562226163775.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Tue, 21 Jul 2020 15:32:39 -0700 (PDT)
> From: Kuniyuki Iwashima <kuniyu@amazon.co.jp>
> Date: Tue, 21 Jul 2020 15:15:29 +0900
>
> > From: kuniyu <kuniyu@amazon.co.jp>
>
> Please fix your configuration to show your full name in this
> "From: " field, I had to edit it out and use the one from your
> email headers.
>
> > This patch set addresses two issues which happen when both connected and
> > unconnected sockets are in the same UDP reuseport group.
>
> Series applied and queued up for -stable, th anks.
I am sorry for bothering you... and grateful for your kind advice.
I have fixed my configuration for net repository as with net-next.
Thank you.
prev parent reply other threads:[~2020-07-22 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 6:15 [PATCH net 0/2] udp: Fix reuseport selection with connected sockets Kuniyuki Iwashima
2020-07-21 6:15 ` [PATCH net 1/2] udp: Copy has_conns in reuseport_grow() Kuniyuki Iwashima
2020-07-21 12:25 ` Willem de Bruijn
2020-07-21 6:15 ` [PATCH net 2/2] udp: Improve load balancing for SO_REUSEPORT Kuniyuki Iwashima
2020-07-21 12:33 ` Willem de Bruijn
2020-07-21 22:32 ` [PATCH net 0/2] udp: Fix reuseport selection with connected sockets David Miller
2020-07-22 4:28 ` Kuniyuki Iwashima [this message]
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=20200722042802.8724-1-kuniyu@amazon.co.jp \
--to=kuniyu@amazon.co.jp \
--cc=benh@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kraig@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=osa-contribution-log@amazon.com \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.org \
/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).