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: Kyle Meyer <kyle.meyer@hpe.com>,
	Kuan-Wei Chiu <visitorckw@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [GIT PULL] bitmap changes for 6.10
Date: Mon, 13 May 2024 09:31:14 -0700	[thread overview]
Message-ID: <ZkJAUsIl07c+dsCc@yury-ThinkPad> (raw)
In-Reply-To: <ZkI/qHXm0x+8MSLR@yury-ThinkPad>

+ linux-kernel@vger.kernel.org

On Mon, May 13, 2024 at 09:28:25AM -0700, Yury Norov wrote:
> The following changes since commit 678e14c772130d3a83225ed56fb9860a40bca38b:
> 
>   Merge tag 'soc-fixes-6.9-1' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc (2024-04-12 13:02:27 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com:/norov/linux.git tags/bitmap-for-6.10
> 
> for you to fetch changes up to c3052c2f53d3546a53f05165a62a2d31abab0e27:
> 
>   usercopy: Don't use "proxy" headers (2024-05-09 09:25:09 -0700)
> 
> ----------------------------------------------------------------
> bitmap patches for 6.10
> 
> Hi Linus,
> 
> Please pull patches for 6.10. This includes:
>  - topology_span_sane() optimization from Kyle Meyer;
>  - fns() rework from Kuan-Wei Chiu and me (used in
>    cpumask_local_spread() and other places); and
>  - headers cleanup from Andy.
> 
> This also adds a MAINTAINERS record for bitops API as it's unattended,
> and I'd like to follow it closer.
> 
> Thanks,
> Yury
> 
> ----------------------------------------------------------------
> Andy Shevchenko (2):
>       bitops: Move aligned_byte_mask() to wordpart.h
>       usercopy: Don't use "proxy" headers
> 
> Kuan-Wei Chiu (2):
>       lib/test_bitops: Add benchmark test for fns()
>       bitops: Optimize fns() for improved performance
> 
> Kyle Meyer (2):
>       cpumask: Add for_each_cpu_from()
>       sched/topology: Optimize topology_span_sane()
> 
> Yury Norov (5):
>       Compiler Attributes: Add __always_used macro
>       lib: make test_bitops compilable into the kernel image
>       bitmap: relax find_nth_bit() limitation on return value
>       bitops: squeeze even more out of fns()
>       MAINTAINERS: add BITOPS API record
> 
>  MAINTAINERS                         | 14 ++++++++++
>  include/linux/bitops.h              | 55 +++++++++++++++++++++++++------------
>  include/linux/compiler_attributes.h | 13 +++++++++
>  include/linux/cpumask.h             | 10 +++++++
>  include/linux/find.h                |  2 +-
>  include/linux/wordpart.h            |  7 +++++
>  kernel/sched/topology.c             |  6 ++--
>  lib/Kconfig.debug                   |  1 -
>  lib/find_bit.c                      |  2 +-
>  lib/test_bitmap.c                   |  4 +--
>  lib/test_bitops.c                   | 28 +++++++++++++++++++
>  lib/usercopy.c                      |  9 ++++--
>  12 files changed, 122 insertions(+), 29 deletions(-)

           reply	other threads:[~2024-05-13 16:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <ZkI/qHXm0x+8MSLR@yury-ThinkPad>]

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=ZkJAUsIl07c+dsCc@yury-ThinkPad \
    --to=yury.norov@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=kyle.meyer@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=torvalds@linux-foundation.org \
    --cc=visitorckw@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®