From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
Michael Lass <bevan@bi-co.net>,
Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fix for 5.2-rc2
Date: Tue, 21 May 2019 19:38:45 -0400 [thread overview]
Message-ID: <20190521233844.GA31426@redhat.com> (raw)
Hi Linus,
The following changes since commit 8454fca4f53bbe5e0a71613192674c8ce5c52318:
dm: fix a couple brace coding style issues (2019-05-16 10:09:21 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.2/dm-fix-1
for you to fetch changes up to 51b86f9a8d1c4bb4e3862ee4b4c5f46072f7520d:
dm: make sure to obey max_io_len_target_boundary (2019-05-21 19:15:20 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix a particularly glaring oversight in a DM core commit from 5.1 that
doesn't properly trim special IOs (e.g. discards) relative to
corresponding target's max_io_len_target_boundary().
----------------------------------------------------------------
Michael Lass (1):
dm: make sure to obey max_io_len_target_boundary
drivers/md/dm.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Michael Lass <bevan@bi-co.net>
Subject: [git pull] device mapper fix for 5.2-rc2
Date: Tue, 21 May 2019 19:38:45 -0400 [thread overview]
Message-ID: <20190521233844.GA31426@redhat.com> (raw)
Hi Linus,
The following changes since commit 8454fca4f53bbe5e0a71613192674c8ce5c52318:
dm: fix a couple brace coding style issues (2019-05-16 10:09:21 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.2/dm-fix-1
for you to fetch changes up to 51b86f9a8d1c4bb4e3862ee4b4c5f46072f7520d:
dm: make sure to obey max_io_len_target_boundary (2019-05-21 19:15:20 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix a particularly glaring oversight in a DM core commit from 5.1 that
doesn't properly trim special IOs (e.g. discards) relative to
corresponding target's max_io_len_target_boundary().
----------------------------------------------------------------
Michael Lass (1):
dm: make sure to obey max_io_len_target_boundary
drivers/md/dm.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
next reply other threads:[~2019-05-21 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 23:38 Mike Snitzer [this message]
2019-05-21 23:38 ` [git pull] device mapper fix for 5.2-rc2 Mike Snitzer
2019-05-22 16:00 ` pr-tracker-bot
2019-05-22 16:00 ` 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=20190521233844.GA31426@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=bevan@bi-co.net \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.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 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.