From: Jakub Kicinski <kuba@kernel.org>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
Mat Martineau <mathew.j.martineau@linux.intel.com>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Martin KaFai Lau <kafai@fb.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next v3 2/3] net: Add bhash2 hashbucket locks
Date: Tue, 14 Jun 2022 18:58:57 -0700 [thread overview]
Message-ID: <20220614185857.771aa2c8@kernel.org> (raw)
In-Reply-To: <CAJnrk1b7F6LMwA9wK-xyimVcGB8mNSn94fL8_Z0SwWnd0uqcmg@mail.gmail.com>
On Tue, 14 Jun 2022 11:08:41 -0700 Joanne Koong wrote:
> I think it's a good idea to revert bhash2 and then I will resubmit
> once all the fixes are in place. Please let me know if there's
> anything I need to do on my side to revert this.
We'd appreciate if you could post a revert patch and gather some of
the history into the commit message (with some Links: to reports and
postings of the fixes if possible).
next prev parent reply other threads:[~2022-06-15 1:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 2:16 [PATCH net-next v3 0/3] bhash2 binding table fixups Joanne Koong
2022-06-11 2:16 ` [PATCH net-next v3 1/3] net: Update bhash2 when socket's rcv saddr changes Joanne Koong
2022-06-12 0:24 ` Kuniyuki Iwashima
2022-06-11 2:16 ` [PATCH net-next v3 2/3] net: Add bhash2 hashbucket locks Joanne Koong
2022-06-11 18:06 ` Eric Dumazet
2022-06-12 0:26 ` Kuniyuki Iwashima
2022-06-13 22:12 ` Mat Martineau
2022-06-14 14:12 ` Paolo Abeni
2022-06-14 18:08 ` Joanne Koong
2022-06-14 18:26 ` Eric Dumazet
2022-06-15 1:58 ` Jakub Kicinski [this message]
2022-06-11 2:16 ` [PATCH net-next v3 3/3] selftests/net: Add sk_bind_sendto_listen test Joanne Koong
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=20220614185857.771aa2c8@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joannelkoong@gmail.com \
--cc=kafai@fb.com \
--cc=mathew.j.martineau@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.