public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Asai Thambi SP <asamymuthupa@micron.com>
Cc: linux-kernel@vger.kernel.org, Sam Bradshaw <sbradshaw@micron.com>,
	Selvan Mani <smani@micron.com>
Subject: Re: [PATCH 0/9] mtip32xx: various fixes
Date: Tue, 16 Jun 2015 08:23:56 -0600	[thread overview]
Message-ID: <5580317C.9070600@kernel.dk> (raw)
In-Reply-To: <55529C37.7060602@micron.com>

On 05/12/2015 06:35 PM, Asai Thambi SP wrote:
> On 5/12/2015 8:39 AM, Jens Axboe wrote:
>> On 05/11/2015 06:47 PM, Asai Thambi SP wrote:
>>> Hi Jens,
>>>
>>> This patchset includes few changes to align with recent kernel changes, few
>>> fixes and cleanup
>>>
>>> Asai Thambi S P (9):
>>>     mtip32xx: fix rmmod issue
>>>     mtip32xx: remove unused variable 'port->allocated'
>>>     mtip32xx: fix incorrectly setting MTIP_DDF_SEC_LOCK_BIT
>>>     mtip32xx: Abort I/O during secure erase operation
>>>     mtip32xx: fix crash on surprise removal of the drive
>>>     mtip32xx: remove unnecessary sleep in mtip_ftl_rebuild_poll()
>>>     mtip32xx: fix minor number
>>>     mtip32xx: abort secure erase operation if the device is mounted
>>>     mtip32xx: increase wait time for hba reset
>>
>> Have these been through one of your qual cycles? Just wondering if I should attempt to squeeze this into the current series, or wait for 4.2.
>>
> Yes, we have tested. You can include in the current series.

I will apply 1-7, and 9. 8 you promised you'd look into a cleaner solution.


-- 
Jens Axboe


  reply	other threads:[~2015-06-16 14:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 22:47 [PATCH 0/9] mtip32xx: various fixes Asai Thambi SP
2015-05-12 15:39 ` Jens Axboe
2015-05-13  0:35   ` Asai Thambi SP
2015-06-16 14:23     ` Jens Axboe [this message]
2015-06-16 16:40       ` Asai Thambi SP

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=5580317C.9070600@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asamymuthupa@micron.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbradshaw@micron.com \
    --cc=smani@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