From: 7091@blargh.com
To: Tejun Heo <teheo@suse.de>
Cc: Tejun Heo <htejun@gmail.com>, Andi Kleen <ak@suse.de>,
7091@blargh.com, linux-ide@vger.kernel.org, jgarzik@pobox.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sata_sil, writing bug with multiple cards?
Date: Wed, 11 Jul 2007 20:21:42 -0700 [thread overview]
Message-ID: <courier.46959E46.00000E8F@blargh.com> (raw)
In-Reply-To: <469365B2.9020809@suse.de>
Tejun Heo writes:
> Please give a shot at the attached patch on top of 2.6.22. Thanks.
Patch applied, but still getting the corruption.
next prev parent reply other threads:[~2007-07-12 3:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <courier.4689EFD9.0000589A@blargh.com>
[not found] ` <468A0E24.7020000@gmail.com>
[not found] ` <courier.468B005A.0000127A@blargh.com>
[not found] ` <courier.468B1258.000018F4@blargh.com>
[not found] ` <courier.468B17B1.00001A78@blargh.com>
2007-07-04 3:53 ` sata_sil, writing bug with multiple cards? Tejun Heo
2007-07-04 7:08 ` Andi Kleen
2007-07-04 8:17 ` 7091
2007-07-04 8:38 ` Andi Kleen
2007-07-04 8:52 ` Tejun Heo
2007-07-10 10:55 ` Tejun Heo
2007-07-12 3:21 ` 7091 [this message]
2007-06-27 21:36 7091
2007-07-08 8:01 ` Janos Haar
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=courier.46959E46.00000E8F@blargh.com \
--to=7091@blargh.com \
--cc=ak@suse.de \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=teheo@suse.de \
/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