From: Jens Axboe <axboe@fb.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Final (final) block IO fixes for 3.14
Date: Mon, 17 Mar 2014 10:32:41 -0600 [thread overview]
Message-ID: <20140317163241.GA23606@kernel.dk> (raw)
Hi Linus,
Yes, the last round was final. This one is final final. The mtip32xx fix
could have waited, but it's so simple and gets rid of two warning
spewages on load. The two block flush fixes are critical for blk-mq, and
are the primary reason for this late pull request.
Please pull!
git://git.kernel.dk/linux-block.git for-linus
for you to fetch changes up to 7f328908f9cb69a72ce1c9279508c786cf85f1f5:
mtip32xx: fix bad use of smp_processor_id() (2014-03-10 14:32:47 -0600)
----------------------------------------------------------------
Jens Axboe (1):
mtip32xx: fix bad use of smp_processor_id()
Mike Snitzer (2):
block: fix q->flush_rq NULL pointer crash on dm-mpath flush
block: change flush sequence list addition back to front add
block/blk-core.c | 17 ++++++-----------
block/blk-flush.c | 11 +++++++----
drivers/block/mtip32xx/mtip32xx.c | 2 +-
3 files changed, 14 insertions(+), 16 deletions(-)
--
Jens Axboe
reply other threads:[~2014-03-17 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140317163241.GA23606@kernel.dk \
--to=axboe@fb.com \
--cc=linux-kernel@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