From: Tejun Heo <tj@kernel.org>
To: Mark Lord <kernel@teksavvy.com>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH] sata_mv: fix broken DSM/TRIM support (v2)
Date: Mon, 23 Aug 2010 15:59:32 +0200 [thread overview]
Message-ID: <4C727EC4.6060903@kernel.org> (raw)
In-Reply-To: <4C727D93.4000105@teksavvy.com>
On 08/23/2010 03:54 PM, Mark Lord wrote:
> On 10-08-23 09:47 AM, Tejun Heo wrote:
>> On 08/23/2010 03:41 PM, Mark Lord wrote:
>>>> Don't we need this for other BMDMA commands too? If so, maybe it's
>>>> better to make it two patches?
>>>
>>>
>>> TRIM is the first/only command which actually breaks
>>> without this. It is possible that other commands may
>>> benefit as well on some DVD-RW drives, but I have not
>>> encountered those yet.
>>>
>>> So for now, I've left it as a single patch,
>>> with all of the (small) pieces together for TRIM.
>>
>> I see. Looks good to me then.
>>
>> Acked-by: Tejun Heo<tj@kernel.org>
> ..
>
> Peachy. I do imagine that both of these patches
> might also be prime candidates for -stable,
> if/when they ever make it upstream.
Just add Cc: stable@kernel.org below SOB's. Greg will be
automatically notified when these patches hit mainline.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-08-23 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 1:19 [PATCH] sata_mv: fix broken DSM/TRIM support Mark Lord
2010-08-20 1:40 ` [PATCH] sata_mv: fix broken DSM/TRIM support (v2) Mark Lord
2010-08-20 13:56 ` Mark Lord
2010-08-20 14:13 ` [PATCH] libata-sff: remove harmful BUG_ON from ata_bmdma_qc_issue Mark Lord
2010-08-23 8:17 ` Tejun Heo
2010-08-23 8:22 ` [PATCH] sata_mv: fix broken DSM/TRIM support (v2) Tejun Heo
2010-08-23 13:41 ` Mark Lord
2010-08-23 13:47 ` Tejun Heo
2010-08-23 13:54 ` Mark Lord
2010-08-23 13:59 ` Tejun Heo [this message]
2010-08-23 13:50 ` Mark Lord
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=4C727EC4.6060903@kernel.org \
--to=tj@kernel.org \
--cc=jeff@garzik.org \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).