From: Asai Thambi SP <asamymuthupa@micron.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: <linux-kernel@vger.kernel.org>,
Sam Bradshaw <sbradshaw@micron.com>,
Selvan Mani <smani@micron.com>,
Rajesh Kumar Sambandam <rsambandam@micron.com>,
Vignesh Gunasekaran <vgunasekaran@micron.com>
Subject: Re: [PATCH 00/10] mtip32xx: various fixes
Date: Tue, 23 Feb 2016 18:12:44 -0800 [thread overview]
Message-ID: <91f99f09-1a6e-2eeb-5f3d-489324f8e853@micron.com> (raw)
In-Reply-To: <20160223161455.GB13712@kernel.dk>
On 2/23/2016 8:14 AM, Jens Axboe wrote:
> On Mon, Feb 22 2016, Asai Thambi SP wrote:
>> Hi Jens,
>>
>> This patchset includes various fixes for mtip32xx driver, tested
>> on kernel 4.5-rc3
>>
>> Selvan Mani (10):
>> mtip32xx: Abort secure erase when drive is mounted
>> mtip32xx: Fix broken service thread handling
>> mtip32xx: Remove unwanted code from taskfile error handler
>> mtip32xx: Print exact time when an internal command is interrupted
>> mtip32xx: Avoid issuing standby immediate cmd during FTL rebuild
>> mtip32xx: Fix for rmmod crash when drive is in FTL rebuild
>> mtip32xx: Handle safe removal during IO
>> mtip32xx: Handle FTL rebuild failure state during device
>> initialization
>> mtip32xx: Add timeout handler
>> mtip32xx: Cleanup queued requests after surprise removal
>
> All your patches are mangled, very white space damaged (tabs are 4
> spaces, etc). As mentioned, I don't think the first patch should go in,
> the rest look fine.
>
I had my email client configured correctly, not sure how the setting changed. I will fix the formatting and resend the patchset.
prev parent reply other threads:[~2016-02-24 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 4:58 Asai Thambi SP
2016-02-23 16:14 ` Jens Axboe
2016-02-24 2:12 ` Asai Thambi SP [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=91f99f09-1a6e-2eeb-5f3d-489324f8e853@micron.com \
--to=asamymuthupa@micron.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=rsambandam@micron.com \
--cc=sbradshaw@micron.com \
--cc=smani@micron.com \
--cc=vgunasekaran@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
all inboxes | Powered by JetHome®