All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
	Alasdair G Kergon <agk@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fix for 6.1-rc2
Date: Tue, 18 Oct 2022 14:44:35 -0400	[thread overview]
Message-ID: <Y070ExTjLGLStSQ0@redhat.com> (raw)

Hi Linus,

The following changes since commit bb1a1146467ad812bb65440696df0782e2bc63c8:

  Merge tag 'cgroup-for-6.1-rc1-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup (2022-10-17 18:52:43 -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.1/dm-fix

for you to fetch changes up to 141b3523e9be6f15577acf4bbc3bc1f82d81d6d1:

  dm bufio: use the acquire memory barrier when testing for B_READING (2022-10-18 12:38:16 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix dm-bufio to use test_bit_acquire to properly test_bit on arches
  with weaker memory ordering.

----------------------------------------------------------------
Mikulas Patocka (1):
      dm bufio: use the acquire memory barrier when testing for B_READING

 drivers/md/dm-bufio.c | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
	Mikulas Patocka <mpatocka@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: [dm-devel] [git pull] device mapper fix for 6.1-rc2
Date: Tue, 18 Oct 2022 14:44:35 -0400	[thread overview]
Message-ID: <Y070ExTjLGLStSQ0@redhat.com> (raw)

Hi Linus,

The following changes since commit bb1a1146467ad812bb65440696df0782e2bc63c8:

  Merge tag 'cgroup-for-6.1-rc1-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup (2022-10-17 18:52:43 -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.1/dm-fix

for you to fetch changes up to 141b3523e9be6f15577acf4bbc3bc1f82d81d6d1:

  dm bufio: use the acquire memory barrier when testing for B_READING (2022-10-18 12:38:16 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix dm-bufio to use test_bit_acquire to properly test_bit on arches
  with weaker memory ordering.

----------------------------------------------------------------
Mikulas Patocka (1):
      dm bufio: use the acquire memory barrier when testing for B_READING

 drivers/md/dm-bufio.c | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


             reply	other threads:[~2022-10-18 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 18:44 Mike Snitzer [this message]
2022-10-18 18:44 ` [dm-devel] [git pull] device mapper fix for 6.1-rc2 Mike Snitzer
2022-10-21  0:41 ` pr-tracker-bot
2022-10-21  0:41   ` [dm-devel] " 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=Y070ExTjLGLStSQ0@redhat.com \
    --to=snitzer@kernel.org \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mpatocka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.