From: Yury Norov <yury.norov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Randy Dunlap <rdunlap@infradead.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Yury Norov <yury.norov@gmail.com>
Subject: Re: [GIT PULL] bitmap: fixes for v6.5-rc5
Date: Mon, 31 Jul 2023 14:04:02 -0700 [thread overview]
Message-ID: <ZMghwgp2/P/WIn5h@yury-ThinkPad> (raw)
In-Reply-To: <ZMgg6OhBN4GzrYyA@yury-ThinkPad>
(Sorry, accidentally dropped CC section.)
On Mon, Jul 31, 2023 at 02:00:27PM -0700, Yury Norov wrote:
> Hi Linus,
>
> Please pull bitmap fixes for v6.5-rc5.
>
> The 2nd patch in the series fixes (workarounds) build for CLANG+GCOV+KASAN
> configuration, so I believe it's worth to merge it in current merging cycle.
>
> The patches spent for ~2 weeks in -next with no issues.
>
> Thanks,
> Yury
>
> The following changes since commit fdf0eaf11452d72945af31804e2a1048ee1b574c:
>
> Linux 6.5-rc2 (2023-07-16 15:10:37 -0700)
>
> are available in the Git repository at:
>
> https://github.com:/norov/linux.git tags/bitmap-6.5-rc5
>
> for you to fetch changes up to 2356d198d2b4ddec24efea98271cb3be230bc787:
>
> lib/bitmap: workaround const_eval test build failure (2023-07-18 13:25:37 -0700)
>
> ----------------------------------------------------------------
> bitmap fixes for v6.5
>
> - Fix for bitmap documentation;
> - Fix for kernel build under certain configuration.
>
> ----------------------------------------------------------------
> Randy Dunlap (1):
> cpumask: eliminate kernel-doc warnings
>
> Yury Norov (1):
> lib/bitmap: workaround const_eval test build failure
>
> include/linux/cpumask.h | 8 ++++++--
> lib/Makefile | 6 ++++++
> lib/cpumask.c | 5 ++++-
> lib/test_bitmap.c | 8 ++++----
> 4 files changed, 20 insertions(+), 7 deletions(-)
>
parent reply other threads:[~2023-07-31 21:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ZMgg6OhBN4GzrYyA@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=ZMghwgp2/P/WIn5h@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=aleksander.lobakin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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®