From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Alexander Potapenko <glider@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
<netdev@vger.kernel.org>, <linux-btrfs@vger.kernel.org>,
<dm-devel@redhat.com>, <ntfs3@lists.linux.dev>,
<linux-s390@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 00/11] bitmap: prereqs for ip_tunnel flags conversion
Date: Mon, 20 Nov 2023 12:04:25 +0100 [thread overview]
Message-ID: <76fe4252-dc61-4d1f-891e-e1cf47da728d@intel.com> (raw)
In-Reply-To: <20231113173717.927056-1-aleksander.lobakin@intel.com>
From: Alexander Lobakin <aleksander.lobakin@intel.com>
Date: Mon, 13 Nov 2023 18:37:06 +0100
> Based on top of "lib/bitmap: add bitmap_{read,write}()"[0] from Alexander
> Potapenko as it uses those new bitmap_{read,write}() functions to not
> introduce another pair of similar ones.
>
> Derived from the PFCP support series[1] as this grew bigger (2 -> 13
> commits in v2) and involved more core bitmap changes, finally transforming
> into a pure bitmap series. The actual mentioned ip_tunnel flags conversion
> from `__be16` to bitmaps will be submitted bundled with the PFCP set after
> this one lands.
>
> Little breakdown:
> * #1, #8, #10: misc cleanups;
> * #2, #5, #6, #7: symbol scope, name collisions;
> * #3, #4, #9, #11: compile-time optimizations.
Ping?
>
> [0] https://lore.kernel.org/lkml/20231109151106.2385155-1-glider@google.com
> [1] https://lore.kernel.org/netdev/20230721071532.613888-1-marcin.szycik@linux.intel.com
[...]
Thanks,
Olek
prev parent reply other threads:[~2023-11-20 11:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 17:37 [PATCH v3 00/11] bitmap: prereqs for ip_tunnel flags conversion Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 01/11] bitops: add missing prototype check Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 02/11] bitops: make BYTES_TO_BITS() treewide-available Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 03/11] bitops: let the compiler optimize {__,}assign_bit() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 04/11] linkmode: convert linkmode_{test,set,clear,mod}_bit() to macros Alexander Lobakin
2023-11-13 19:08 ` Andrew Lunn
2023-11-13 17:37 ` [PATCH v3 05/11] s390/cio: rename bitmap_size() -> idset_bitmap_size() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 06/11] fs/ntfs3: add prefix to bitmap_size() and use BITS_TO_U64() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 07/11] btrfs: rename bitmap_set_bits() -> btrfs_bitmap_set_bits() Alexander Lobakin
2023-11-14 0:48 ` Anand Jain
2023-11-13 17:37 ` [PATCH v3 08/11] tools: move alignment-related macros to new <linux/align.h> Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 09/11] bitmap: introduce generic optimized bitmap_size() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 10/11] bitmap: make bitmap_{get,set}_value8() use bitmap_{read,write}() Alexander Lobakin
2023-11-13 17:37 ` [PATCH v3 11/11] lib/bitmap: add compile-time test for __assign_bit() optimization Alexander Lobakin
2023-11-20 11:04 ` Alexander Lobakin [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=76fe4252-dc61-4d1f-891e-e1cf47da728d@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dm-devel@redhat.com \
--cc=glider@google.com \
--cc=kuba@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=netdev@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=przemyslaw.kitszel@intel.com \
--cc=yury.norov@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 read-only IMAP folder(s) and NNTP newsgroup(s).