From: Jens Axboe <axboe@kernel.dk>
To: Asai Thambi S P <asamymuthupa@micron.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Sam Bradshaw <sbradshaw@micron.com>
Subject: Re: [PATCH v2 0/7] mtip32xx: Add support for device status and other changes
Date: Mon, 09 Apr 2012 08:36:40 +0200 [thread overview]
Message-ID: <4F828378.9060808@kernel.dk> (raw)
In-Reply-To: <4F824919.3090600@micron.com>
On 2012-04-09 04:27, Asai Thambi S P wrote:
>
> This patchset adds support for new sysfs entry 'status' and other
> changes like merging various flag variables, handling of commands.
> This also includes the new ABI file for this driver (Reported-by:
> Greg Kroah-Hartman).
>
> I have split the couple of patches as suggested by Jens, and
> maintained the order of the patches as in previous version. That is
> the reason for 'misc changes' patch being in the middle.
Thanks, this looks better and it applies fine as well. Applied 1-7.
--
Jens Axboe
prev parent reply other threads:[~2012-04-09 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 2:27 [PATCH v2 0/7] mtip32xx: Add support for device status and other changes Asai Thambi S P
2012-04-09 6:36 ` Jens Axboe [this message]
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=4F828378.9060808@kernel.dk \
--to=axboe@kernel.dk \
--cc=asamymuthupa@micron.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sbradshaw@micron.com \
/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.