From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Kuan-Wei Chiu <visitorckw@gmail.com>,
Ken Raeburn <raeburn@redhat.com>, Arnd Bergmann <arnd@arndb.de>
Subject: [git pull] device mapper fixes for 6.9-rc2
Date: Fri, 29 Mar 2024 10:20:22 -0400 [thread overview]
Message-ID: <ZgbOJlMv2nYOEbWe@redhat.com> (raw)
Hi Linus,
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.9/dm-fixes-2
for you to fetch changes up to 8e91c2342351e0f5ef6c0a704384a7f6fc70c3b2:
dm integrity: fix out-of-range warning (2024-03-29 09:48:07 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix MAINTAINERS to not include M: dm-devel for DM entries.
- Fix DM vdo's murmurhash to use proper byteswapping methods.
- Fix DM integrity clang warning about comparison out-of-range.
-----BEGIN PGP SIGNATURE-----
iQEzBAABCAAdFiEEJfWUX4UqZ4x1O2wixSPxCi2dA1oFAmYGzUoACgkQxSPxCi2d
A1roewf/V6P7fvYKJlAFQ3nhpOy09KSY8G1UofjrfTmqVG329jAzOWoEq5umivPY
TLWJ0kJ1Wst0+U61u+lho0RnYd3ZHQU3pMrl5Lq9B5yCeZcZIPYxhEBhBsRJtSV7
m04aaF8Lox5ofhPfNwrhUmJyTa7ZKtkz2MCk4TaT3qNkamzE0ToYjJduERzA1FU7
x8fEg/D8CrPVn5tbTf6G2u3T2iMJXu1mzR3bj3C8CEGN4QPtRc9c54s2FL4o0mOS
c/i7VDSSDk/NujY65vY2u0P3hNZKEUcv00M7LezYA6hwhZdINTS4K4oOtPaZUYaN
FsjMHiyE5echCCv6FvE+ztFGo4H30w==
=U7Wa
-----END PGP SIGNATURE-----
----------------------------------------------------------------
Arnd Bergmann (1):
dm integrity: fix out-of-range warning
Ken Raeburn (1):
dm vdo murmurhash3: use kernel byteswapping routines instead of GCC ones
Kuan-Wei Chiu (1):
MAINTAINERS: Remove incorrect M: tag for dm-devel@lists.linux.dev
MAINTAINERS | 2 --
drivers/md/dm-integrity.c | 2 +-
drivers/md/dm-vdo/murmurhash3.c | 33 ++++++++-------------------------
3 files changed, 9 insertions(+), 28 deletions(-)
next reply other threads:[~2024-03-29 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 14:20 Mike Snitzer [this message]
2024-03-29 19:27 ` [git pull] device mapper fixes for 6.9-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=ZgbOJlMv2nYOEbWe@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=arnd@arndb.de \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=raeburn@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).