From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <sdf@fomichev.me>
Cc: <andrew+netdev@lunn.ch>, <atenart@kernel.org>,
<davem@davemloft.net>, <edumazet@google.com>, <enjuk@amazon.com>,
<horms@kernel.org>, <jasowang@redhat.com>, <jdamato@fastly.com>,
<kory.maincent@bootlin.com>, <kuba@kernel.org>,
<kuniyu@amazon.com>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<willemdebruijn.kernel@gmail.com>
Subject: Re: [PATCH net-next 1/2] Revert "net: replace dev_addr_sem with netdev instance lock"
Date: Tue, 11 Mar 2025 19:11:30 -0700 [thread overview]
Message-ID: <20250312021132.67611-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250311084507.3978048-2-sdf@fomichev.me>
From: Stanislav Fomichev <sdf@fomichev.me>
Date: Tue, 11 Mar 2025 01:45:06 -0700
> This reverts commit df43d8bf10316a7c3b1e47e3cc0057a54df4a5b8.
>
> Cc: Kohei Enju <enjuk@amazon.com>
> Fixes: df43d8bf1031 ("net: replace dev_addr_sem with netdev instance lock")
>
nit: no newline :)
> Signed-off-by: Stanislav Fomichev <sdf@fomichev.me>
Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
next prev parent reply other threads:[~2025-03-12 2:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 8:45 [PATCH net-next 0/2] net: bring back dev_addr_sem Stanislav Fomichev
2025-03-11 8:45 ` [PATCH net-next 1/2] Revert "net: replace dev_addr_sem with netdev instance lock" Stanislav Fomichev
2025-03-12 2:11 ` Kuniyuki Iwashima [this message]
2025-03-11 8:45 ` [PATCH net-next 2/2] net: reorder dev_addr_sem lock Stanislav Fomichev
2025-03-12 2:27 ` Kuniyuki Iwashima
2025-03-12 8:59 ` Stanislav Fomichev
2025-03-12 13:25 ` [PATCH net-next 0/2] net: bring back dev_addr_sem Lei Yang
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=20250312021132.67611-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enjuk@amazon.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=jdamato@fastly.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=willemdebruijn.kernel@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).