From: Asai Thambi S P <asamymuthupa@micron.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Sam Bradshaw" <sbradshaw@micron.com>
Subject: Re: [PATCH 2/2] mtip32xx: mtip32xx: Disable TRIM support
Date: Tue, 16 Apr 2013 00:35:43 +0530 [thread overview]
Message-ID: <516C4F87.2050104@micron.com> (raw)
In-Reply-To: <20130414082522.GE12244@kernel.dk>
On 4/14/2013 1:55 PM, Jens Axboe wrote:
> On Fri, Apr 12 2013, Asai Thambi S P wrote:
>>
>> Temporarily disabling TRIM support until TRIM related issues
>> are addressed in the firmware.
>
> How serious is this? We do have released kernels out there with the
> driver, you might want to consider a stable backport too.
>
> Anyway, applied for 3.10.
>
Added TRIM support in 3.9 merge window. If this trivial change could be
pushed, it would be good. Otherwise, I can backport to stable 3.9 when released.
--
regards,
asai
prev parent reply other threads:[~2013-04-15 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 18:28 [PATCH 2/2] mtip32xx: mtip32xx: Disable TRIM support Asai Thambi S P
2013-04-14 8:25 ` Jens Axboe
2013-04-15 16:41 ` Sam Bradshaw (sbradshaw)
2013-04-15 19:05 ` Asai Thambi S P [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=516C4F87.2050104@micron.com \
--to=asamymuthupa@micron.com \
--cc=axboe@kernel.dk \
--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