From: Simon Horman <simon.horman@corigine.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH v1 1/2] net/core: Make use of assign_bit() API
Date: Thu, 29 Jun 2023 17:19:47 +0200 [thread overview]
Message-ID: <ZJ2hE5sUnd86Nc0O@corigine.com> (raw)
In-Reply-To: <20230629132240.80372-1-andriy.shevchenko@linux.intel.com>
On Thu, Jun 29, 2023 at 04:22:39PM +0300, Andy Shevchenko wrote:
> We have for some time the assign_bit() API to replace open coded
>
> if (foo)
> set_bit(n, bar);
> else
> clear_bit(n, bar);
>
> Use this API in the code. No functional change intended.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Hi Andy,
I'm assuming this is targeted at 'net-next', as opposed to 'net', which is
for fixes. In any case, the target tree should be included in the subject.
Subject: [PATCH net-next v2] ...
If it is for net-next, then please repost when net-next reopens after July 10th.
Link: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: deferred
prev parent reply other threads:[~2023-06-29 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 13:22 [PATCH v1 1/2] net/core: Make use of assign_bit() API Andy Shevchenko
2023-06-29 13:22 ` [PATCH v1 2/2] netlink: Make use of __assign_bit() API Andy Shevchenko
2023-06-29 15:19 ` Simon Horman [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=ZJ2hE5sUnd86Nc0O@corigine.com \
--to=simon.horman@corigine.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.