mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Randy Dunlap <rdunlap@infradead.org>,
	Gavin Shan <gshan@redhat.com>, Guenter Roeck <linux@roeck-us.net>,
	Yury Norov <yury.norov@gmail.com>
Subject: [GIT PULL] bitmap changes for v6.5-rc1
Date: Sun, 2 Jul 2023 10:30:24 -0700	[thread overview]
Message-ID: <ZKG0MO5/1SgEobf5@yury-ThinkPad> (raw)

Hi Linus,

Please pull bitmap changes for 6.5-rc1. They spent for more than a
week in -next without any issues.

Thanks,
Yury

The following changes since commit dad9774deaf1cf8e8f7483310dfb2690310193d2:

  Merge tag 'timers-urgent-2023-06-21' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2023-06-21 12:36:34 -0700)

are available in the Git repository at:

  https://github.com:/norov/linux.git/bitmap-6.5-rc1 bitmap-6.5-rc1

for you to fetch changes up to 2a3110e3f97ddc0f53bb766797b926a35edd07e6:

  MAINTAINERS: Add bitfield.h to the BITMAP API record (2023-06-22 13:57:42 -0700)

----------------------------------------------------------------
bitmap patches for v6.5

Fixes for different bitmap pieces:

 - lib/test_bitmap: increment failure counter properly

   The tests that don't use expect_eq() macro to determine that a test is
   failured must increment failed_tests explicitly.

 - lib/bitmap: drop optimization of bitmap_{from,to}_arr64

   bitmap_{from,to}_arr64() optimization is overly optimistic on 32-bit LE
   architectures when it's wired to bitmap_copy_clear_tail().

 - nodemask: Drop duplicate check in for_each_node_mask()

   As the return value type of first_node() became unsigned, the node >= 0
   became unnecessary.

 - cpumask: fix function description kernel-doc notation

 - MAINTAINERS: Add bits.h to the BITMAP API record
 - MAINTAINERS: Add bitfield.h to the BITMAP API record

   Add linux/bits.h and linux/bitfield.h for visibility

----------------------------------------------------------------
Andy Shevchenko (2):
      MAINTAINERS: Add bits.h to the BITMAP API record
      MAINTAINERS: Add bitfield.h to the BITMAP API record

Gavin Shan (1):
      nodemask: Drop duplicate check in for_each_node_mask()

Randy Dunlap (1):
      cpumask: fix function description kernel-doc notation

Yury Norov (2):
      lib/test_bitmap: increment failure counter properly
      lib/bitmap: drop optimization of bitmap_{from,to}_arr64

 MAINTAINERS              |  6 ++++++
 include/linux/bitmap.h   |  8 +++-----
 include/linux/nodemask.h |  2 +-
 lib/bitmap.c             |  2 +-
 lib/cpumask.c            |  2 +-
 lib/test_bitmap.c        | 18 +++++++++++++++---
 6 files changed, 27 insertions(+), 11 deletions(-)

             reply	other threads:[~2023-07-02 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 17:30 Yury Norov [this message]
2023-07-08 19:18 ` pr-tracker-bot

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=ZKG0MO5/1SgEobf5@yury-ThinkPad \
    --to=yury.norov@gmail.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gshan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=linux@roeck-us.net \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    /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®