From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org, axboe@kernel.dk
Subject: [git pull] device mapper induced block fix for 5.10-rc7
Date: Fri, 4 Dec 2020 18:12:26 -0500 [thread overview]
Message-ID: <20201204231225.GA4574@redhat.com> (raw)
In-Reply-To: <20201204223742.GA82260@lobo>
Hi Linus (and Jens),
Apologies for the glaring bug I introduced with my previous pull request!
The following changes since commit bde3808bc8c2741ad3d804f84720409aee0c2972:
dm: remove invalid sparse __acquires and __releases annotations (2020-12-04 15:25:18 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.10/dm-fixes-2
for you to fetch changes up to 65f33b35722952fa076811d5686bfd8a611a80fa:
block: fix incorrect branching in blk_max_size_offset() (2020-12-04 17:27:42 -0500)
Please pull, thanks!
Mike
----------------------------------------------------------------
Fix incorrect branching at top of blk_max_size_offset().
----------------------------------------------------------------
Mike Snitzer (1):
block: fix incorrect branching in blk_max_size_offset()
include/linux/blkdev.h | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
next prev parent reply other threads:[~2020-12-04 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 21:05 [git pull] device mapper fixes for 5.10-rc7 Mike Snitzer
2020-12-04 21:35 ` pr-tracker-bot
2020-12-04 22:37 ` [PATCH] block: fix incorrect branching in blk_max_size_offset() [was: Re: [git pull] device mapper fixes for 5.10-rc7] Mike Snitzer
2020-12-04 23:12 ` Mike Snitzer [this message]
2020-12-05 19:21 ` [dm-devel] [git pull] device mapper induced block fix for 5.10-rc7 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=20201204231225.GA4574@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox