public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Sam Bradshaw <sbradshaw@micron.com>
Subject: Re: [PATCH 0/5] mtip32xx: Add support for device status and some optimitizations
Date: Fri, 06 Apr 2012 11:39:38 -0600	[thread overview]
Message-ID: <4F7F2A5A.6010107@kernel.dk> (raw)
In-Reply-To: <4F7F2A01.6050806@micron.com>

On 2012-04-06 11:38, Asai Thambi S P wrote:
> On 4/5/2012 5:21 PM, Jens Axboe wrote:
> 
>> On 2012-04-05 14:59, Asai Thambi S P wrote:
>>>
>>> This patchset adds support for new sysfs entry 'status', fix in restart port,
>>> and some optimizations like merging various flag variables. 
>>>
>>> Asai Thambi S P (5):
>>>   mtip32xx: Add new bitwise flag 'dd_flag' and make set comp_time as
>>>     common
>>>   mtip32xx: Add new sysfs entry 'status' and fix restart port
>>>   mtip32xx: Shorten macro names
>>>   mtip32xx: handling of commands in various scenarios
>>>   mtip32xx: dump tagmap on failure
>>>
>>>  drivers/block/mtip32xx/mtip32xx.c |  844 +++++++++++++++++++++++++++++--------
>>>  drivers/block/mtip32xx/mtip32xx.h |   58 ++-
>>>  2 files changed, 702 insertions(+), 200 deletions(-)
>>
>> These are not applying to for-3.4/drivers, so I can't apply them as-is.
>>
> 
> 
> Sorry, patches were based on master. I will re-base for-3.4/drivers

Thanks, there's a mtip32xx patch in there already, so that's probably
what is causing the issue.

-- 
Jens Axboe


      reply	other threads:[~2012-04-06 17:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 20:59 [PATCH 0/5] mtip32xx: Add support for device status and some optimitizations Asai Thambi S P
2012-04-06  0:21 ` Jens Axboe
2012-04-06 17:38   ` Asai Thambi S P
2012-04-06 17:39     ` 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=4F7F2A5A.6010107@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asamymuthupa@micron.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox