From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: michal.kepien@poczta.onet.pl, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH pata-2.6 fix queue] hpt366: don't check enablebits for HPT36x
Date: Sat, 5 May 2007 23:20:16 +0200 [thread overview]
Message-ID: <200705052320.16144.bzolnier@gmail.com> (raw)
In-Reply-To: <463CE681.9050000@ru.mvista.com>
On Saturday 05 May 2007, Sergei Shtylyov wrote:
> Hello.
>
> Bartlomiej Zolnierkiewicz wrote:
>
> >>HPT36x chip don't seem to have the channel enable bits, so prevent the IDE core
> >>from checking them...
>
> >>Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
>
> > applied
>
> I'm getting "403 Forbidden" trying to browse this patch (and
> ide-cs-recognize-2gb-compactflash-from-transcend.patch as well).
Should be fixed now - sorry for that.
While at it I replaced mine version of "the hpt366: simplify UltraDMA
filtering (take 2)" with the official one ;) and fixed my damn scripts
to always do "chmod 644 pata-2.6/patches/*.patch" before pushing updates
to kernel.org.
Bart
next prev parent reply other threads:[~2007-05-05 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 19:18 [PATCH pata-2.6 fix queue] hpt366: don't check enablebits for HPT36x Sergei Shtylyov
2007-05-05 19:30 ` Bartlomiej Zolnierkiewicz
2007-05-05 20:18 ` Sergei Shtylyov
2007-05-05 21:20 ` Bartlomiej Zolnierkiewicz [this message]
2007-05-06 22:53 ` Andries Brouwer
2007-05-24 20:23 ` Sergei Shtylyov
2007-05-24 20:34 ` Linas Vepstas
2007-05-24 20:53 ` Sergei Shtylyov
2007-05-24 21:06 ` Linas Vepstas
2007-05-24 21:47 ` Sergei Shtylyov
2007-05-25 17:58 ` Linas Vepstas
2007-05-25 18:12 ` Sergei Shtylyov
2007-05-28 20:32 ` Andries Brouwer
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=200705052320.16144.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.kepien@poczta.onet.pl \
--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).