From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: haozhe chang <haozhe.chang@mediatek.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Loic Poulain <loic.poulain@linaro.org>,
Sergey Ryazanov <ryazanov.s.a@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v1 1/1] wwan: core: Use the bitmap API to allocate bitmaps
Date: Tue, 29 Aug 2023 16:26:58 +0300 [thread overview]
Message-ID: <ZO3yIo3tGb8NRiy6@smile.fi.intel.com> (raw)
In-Reply-To: <20230828124524.5ca4da50@kernel.org>
On Mon, Aug 28, 2023 at 12:45:24PM -0700, Jakub Kicinski wrote:
> On Mon, 28 Aug 2023 16:19:53 +0300 Andy Shevchenko wrote:
> > Use bitmap_zalloc() and bitmap_free() instead of hand-writing them.
> > It is less verbose and it improves the type checking and semantic.
> >
> > While at it, add missing header inclusion (should be bitops.h,
> > but with the above change it becomes bitmap.h).
>
> ## Form letter - net-next-closed
>
> The merge window for v6.6 has begun and therefore net-next is closed
> for new drivers, features, code refactoring and optimizations.
> We are currently accepting bug fixes only.
Sure.
> Please repost when net-next reopens after Sept 11th.
I'm wondering since we have established lore archive along with `b4` or any
analogous tool (since there is an API) why I need to repost. It increases
the SNR in the mailing lists, consumes more resources —> adds into global
climate change.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-08-29 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 13:19 Andy Shevchenko
2023-08-28 18:06 ` Sergey Ryazanov
2023-08-29 13:24 ` Andy Shevchenko
2023-08-28 19:45 ` Jakub Kicinski
2023-08-29 13:26 ` Andy Shevchenko [this message]
2023-08-30 13:48 ` Loic Poulain
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=ZO3yIo3tGb8NRiy6@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haozhe.chang@mediatek.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryazanov.s.a@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
all inboxes | Powered by JetHome®