[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f10e8993-3b99-4fde-b7e6-cc459b7b6021@web.de>
Date: Wed, 8 May 2024 14:07:18 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Ziwei Xiao <ziweixiao@...gle.com>, netdev@...r.kernel.org,
kernel-janitors@...r.kernel.org,
Harshitha Ramamurthy <hramamurthy@...gle.com>,
Praveen Kaligineedi <pkaligineedi@...gle.com>,
Willem de Bruijn <willemb@...gle.com>
Cc: LKML <linux-kernel@...r.kernel.org>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Jeroen de Borst <jeroendb@...gle.com>,
John Fraker <jfraker@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Shailend Chand <shailend@...gle.com>, rushilg@...gle.com
Subject: Re: [PATCH net-next 1/5] gve: Add adminq mutex lock
…
> the rtnl_lock, such as the upcoming flow steering operations. For such
> situations, it can temporarily drop the rtnl_lock, and replace it for
> these operations with a new adminq lock, which can ensure the adminq
> command execution to be thread-safe.
Would you like to use imperative wordings for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc7#n94
Regards,
Markus
Powered by blists - more mailing lists