From: Jens Axboe <jaxboe@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] followup block pull request
Date: Thu, 31 May 2012 14:12:06 +0200 [thread overview]
Message-ID: <4FC76016.3040108@fusionio.com> (raw)
Hi Linus,
Includes the fix from Eric to resolve the infinite loop in looking up /
creating an IO context for an exiting task.
Also a bunch of mtip32xx patches. Fairly trivial stuff. It's fairly new
though, but no point in keeping it out of the tree until 3.6 imho. I've
thrown it through basic testing locally as well, works fine. The one
contentious part is the patch that Greg complained about (sysfs file
with multiple values, should be a debugfs file), which is perfectly
valid, but not a regression from what the file contains now. That will
be fixed up separately.
git://git.kernel.dk/linux-block.git for-linus
----------------------------------------------------------------
Asai Thambi S P (10):
mtip32xx: fix clearing an incorrect register in mtip_init_port
mtip32xx: Set custom timeouts for PIO commands
mtip32xx: Change HDIO_GET_IDENTITY to return stored data
mtip32xx: Fix to handle TFE for PIO(IOCTL/internal) commands
mtip32xx: Set block queue boundary variables
mtip32xx: Use plain spinlock for 'cmd_issue_lock'
mtip32xx: Fix to support more than one sector in exec_drive_command()
mtip32xx: minor performance tweak
mtip32xx: Convert macro definitions for flag bits to enum
mtip32xx: Changes to sysfs entries
Eric Dumazet (1):
block: avoid infinite loop in get_task_io_context()
Documentation/ABI/testing/sysfs-block-rssd | 12 +-
block/blk-ioc.c | 6 +-
drivers/block/mtip32xx/mtip32xx.c | 276 ++++++++++++++++++-----------
drivers/block/mtip32xx/mtip32xx.h | 48 ++---
4 files changed, 212 insertions(+), 130 deletions(-)
--
Jens Axboe
reply other threads:[~2012-05-31 12:12 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=4FC76016.3040108@fusionio.com \
--to=jaxboe@fusionio.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