From: Jeff Garzik <jeff@garzik.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] pata_sil680: kill bogus reset code (take 2)
Date: Fri, 23 Nov 2007 19:24:22 -0500 [thread overview]
Message-ID: <47476F36.4030201@garzik.org> (raw)
In-Reply-To: <200711161950.04670.sshtylyov@ru.mvista.com>
Sergei Shtylyov wrote:
> Since writing to two reserved bits ain't much of a housekeeping, I think it's
> time we get rid of the custom error handler in this driver. ;-)
>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
>
> ---
> Oops, somehow I've managed to send a stale patch, without a version change...
> This code has been discussed 4 months ago, and is still in the same state. :-|
> The patch is against the Linus' tree...
>
> drivers/ata/pata_sil680.c | 32 ++------------------------------
> 1 files changed, 2 insertions(+), 30 deletions(-)
applied
prev parent reply other threads:[~2007-11-24 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 16:50 [PATCH] pata_sil680: kill bogus reset code (take 2) Sergei Shtylyov
2007-11-24 0:24 ` Jeff Garzik [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=47476F36.4030201@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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).