mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <ynorov@nvidia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Georgios Androutsopoulos <georgeandrout13@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Shashank Mohan Jain <jain.sm@gmail.com>,
	Yury Norov <ynorov@nvidia.com>,
	linux-kernel@vger.kernel.org
Cc: yury.norov@gmail.com
Subject: [GIT PULL] bitmap updates for 7.4
Date: Sun, 18 Oct 2026 21:24:19 -0400	[thread overview]
Message-ID: <atVxQyCK11nPQsc1@yury> (raw)

Hi Linus,

Please pull bitmap updates for v7.4. It includes __MAKE_OP() macro
removal from me with the follow-up from Mark, cleanups for bitmaps
parser from Shashank and a couple Rust docs fixes from Georgios.

All patches spent in -next for over a month; applied on top of v7.3
and boot-tested with no issues.

Thanks,
Yury


The following changes since commit 93f51579e7df248780214094418f205253383cc5:

  Linux 7.3-rc4 (2026-09-20 13:48:15 -0700)

are available in the Git repository at:

  https://github.com/norov/linux.git tags/bitmap-for-v7.4-rc1

for you to fetch changes up to a73b4d1fa7d334a5f7de5bb0a14726530f66196e:

  rust: bitmap: document panics in `next_bit` and `next_zero_bit` (2026-10-06 12:15:40 -0400)

----------------------------------------------------------------
bitmap updates for v7.4

 - __MAKE_OP() removal (Yury, Mark);
 - bitmap parsing fixes (Shashank);
 - Rust docs updates (Georgios).

----------------------------------------------------------------
Georgios Androutsopoulos (2):
      rust: id_pool: document panics in `find_unused_id` and `release_id`
      rust: bitmap: document panics in `next_bit` and `next_zero_bit`

Mark Brown (1):
      bitfield: Restore be16_replace_bits()

Shashank Mohan Jain (6):
      bitmap: bitmap_parse(): reject non-hex character before 8 digits
      bitmap: test bitmap_parse() with an illegal character before 8 hex digits
      bitmap: bitmap_parselist(): reject trailing characters after group size
      bitmap: test bitmap_parselist() with text after the group size
      bitmap: bitmap_parselist(): don't wrap around on a huge group size
      bitmap: test bitmap_parselist() with a group size close to UINT_MAX

Yury Norov (1):
      bitfield: get rid of __MAKE_OP machinery

 MAINTAINERS                              |   2 +
 include/linux/bitfield-fix-width.h       | 241 +++++++++++++++++++++++++++++++
 include/linux/bitfield.h                 |  49 +------
 lib/bitmap-str.c                         |  24 ++-
 lib/test_bitmap.c                        |   9 ++
 rust/kernel/bitmap.rs                    |  17 ++-
 rust/kernel/id_pool.rs                   |  15 +-
 tools/include/linux/bitfield-fix-width.h | 236 ++++++++++++++++++++++++++++++
 tools/include/linux/bitfield.h           |  49 +------
 9 files changed, 538 insertions(+), 104 deletions(-)
 create mode 100644 include/linux/bitfield-fix-width.h
 create mode 100644 tools/include/linux/bitfield-fix-width.h

                 reply	other threads:[~2026-10-19  1:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=atVxQyCK11nPQsc1@yury \
    --to=ynorov@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=georgeandrout13@gmail.com \
    --cc=jain.sm@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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

all inboxes | Powered by JetHome®