From: Jakub Kicinski <kuba@kernel.org>
To: dccp@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/2] net: Add a second bind table hashed by port and address
Date: Thu, 19 May 2022 15:54:53 +0000 [thread overview]
Message-ID: <20220519085453.1f499514@kernel.org> (raw)
In-Reply-To: <20220519075119.87442-1-kuniyu@amazon.co.jp>
On Thu, 19 May 2022 16:51:19 +0900 Kuniyuki Iwashima wrote:
> To maintainers:
> lore and patchwork seem to miss this version...?
Yeah :( We're trying to debug with Joanne and the vger admin,
if we can't fix it by the end of the day I'll just merge the
last posting that made it thru, IIRC the patches are identical.
Thanks for the review!
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.co.jp>
Cc: <joannelkoong@gmail.com>, <davem@davemloft.net>,
<dsahern@kernel.org>, <edumazet@google.com>, <kafai@fb.com>,
<pabeni@redhat.com>, <richard_siegfried@systemli.org>,
<yoshfuji@linux-ipv6.org>, <netdev@vger.kernel.org>,
<dccp@vger.kernel.org>
Subject: Re: [PATCH net-next v5 1/2] net: Add a second bind table hashed by port and address
Date: Thu, 19 May 2022 08:54:53 -0700 [thread overview]
Message-ID: <20220519085453.1f499514@kernel.org> (raw)
In-Reply-To: <20220519075119.87442-1-kuniyu@amazon.co.jp>
On Thu, 19 May 2022 16:51:19 +0900 Kuniyuki Iwashima wrote:
> To maintainers:
> lore and patchwork seem to miss this version...?
Yeah :( We're trying to debug with Joanne and the vger admin,
if we can't fix it by the end of the day I'll just merge the
last posting that made it thru, IIRC the patches are identical.
Thanks for the review!
next prev parent reply other threads:[~2022-05-19 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 7:51 [PATCH net-next v5 1/2] net: Add a second bind table hashed by port and address Kuniyuki Iwashima
2022-05-19 7:51 ` Kuniyuki Iwashima
2022-05-19 15:54 ` Jakub Kicinski [this message]
2022-05-19 15:54 ` 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=20220519085453.1f499514@kernel.org \
--to=kuba@kernel.org \
--cc=dccp@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.