public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: yury.norov@gmail.com
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Cc: Alice Ryhl <aliceryhl@google.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
	Yury Norov <yury.norov@gmail.com>
Subject: [GIT PULL] bitmap for 6.18-rc2
Date: Wed, 15 Oct 2025 11:38:41 -0400	[thread overview]
Message-ID: <aO_AAQBzqMkrGiry@yury> (raw)

Hi Linus,

Please pull fixes for 6.18-rc2: "unnecessary `unsafe`" warning fix for
bitmap/rust, and one leftover patch for FIELD_PREP_WM16() conversion.

Thanks,
Yury

The following changes since commit 9b332cece987ee1790b2ed4c989e28162fa47860:

  Merge tag 'nfsd-6.18-1' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux (2025-10-14 09:28:12 -0700)

are available in the Git repository at:

  https://github.com/norov/linux.git tags/bitmap-for-v6.18-rc2

for you to fetch changes up to 7e85ac9da1acc591bd5269f2b890ed1994c42e96:

  PM / devfreq: rockchip-dfi: switch to FIELD_PREP_WM16 macro (2025-10-15 10:39:54 -0400)

----------------------------------------------------------------
bitmap-for-6.18-rc2

 - rust: bitmap: clean Rust 1.92.0 `unused_unsafe` warning (Miguel);
 - FIELD_PREP_WM16() rework leftover (Nicolas).

----------------------------------------------------------------
Miguel Ojeda (1):
      rust: bitmap: clean Rust 1.92.0 `unused_unsafe` warning

Nicolas Frattaroli (1):
      PM / devfreq: rockchip-dfi: switch to FIELD_PREP_WM16 macro

 drivers/devfreq/event/rockchip-dfi.c | 45 ++++++++++++++++++------------------
 rust/kernel/bitmap.rs                |  2 ++
 2 files changed, 24 insertions(+), 23 deletions(-)

             reply	other threads:[~2025-10-15 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 15:38 yury.norov [this message]
2025-10-15 16:39 ` [GIT PULL] bitmap for 6.18-rc2 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=aO_AAQBzqMkrGiry@yury \
    --to=yury.norov@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=nicolas.frattaroli@collabora.com \
    --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