From: Tejun Heo <tj@kernel.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Martin Braure de Calignon <braurede@free.fr>,
714295@bugs.debian.org, linux-ide@vger.kernel.org,
risc4all@yahoo.com
Subject: Re: [PATCH libata/for-3.11-fixes] libata: make it clear that sata_inic162x is experimental
Date: Fri, 26 Jul 2013 08:46:23 -0400 [thread overview]
Message-ID: <20130726124623.GA3013@htj.dyndns.org> (raw)
In-Reply-To: <1374814640.13555.1.camel@deadeye.wl.decadent.org.uk>
On Fri, Jul 26, 2013 at 05:57:20AM +0100, Ben Hutchings wrote:
> On Mon, 2013-07-22 at 17:13 -0400, Tejun Heo wrote:
> > Hello, guys.
> >
> > I've committed the following patch to for-3.11-fixes. It's
> > unfortunate but I can't see a good way out at this point. :(
> [...]
>
> This change is also appropriate for a stable update.
Indeed. Will forward the patch to Greg.
> I will also remove the driver from Debian packages.
Yeap, please do so.
Thanks!
--
tejun
next prev parent reply other threads:[~2013-07-26 12:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130627160606.3447.9939.reportbug@storm.xmen.local>
[not found] ` <20130627165114.GK4752@decadent.org.uk>
[not found] ` <1372353297.24346.4.camel@phoenix>
[not found] ` <20130627173142.GM4752@decadent.org.uk>
[not found] ` <1372375714.330.17.camel@phoenix>
[not found] ` <1372383087.23847.35.camel@deadeye.wl.decadent.org.uk>
[not found] ` <1372427725.23094.17.camel@phoenix>
2013-06-30 14:49 ` Data corruption when using INIC-1623TA2 controller Ben Hutchings
2013-07-01 6:17 ` Tejun Heo
2013-07-01 8:52 ` Martin Braure de Calignon
2013-07-22 21:13 ` [PATCH libata/for-3.11-fixes] libata: make it clear that sata_inic162x is experimental Tejun Heo
2013-07-26 4:57 ` Ben Hutchings
2013-07-26 12:46 ` Tejun Heo [this message]
2013-07-29 16:52 ` Tejun Heo
2013-08-01 3:15 ` Greg Kroah-Hartman
2013-08-02 14:44 ` Luis Henriques
2013-08-31 20:17 ` Ben Hutchings
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=20130726124623.GA3013@htj.dyndns.org \
--to=tj@kernel.org \
--cc=714295@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=braurede@free.fr \
--cc=linux-ide@vger.kernel.org \
--cc=risc4all@yahoo.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;
as well as URLs for NNTP newsgroup(s).