From: Arjan van de Ven <arjanv@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: willy@debian.org, linux-scsi@vger.kernel.org
Subject: Re: i450nx-scanning-fix.patch
Date: Mon, 29 Dec 2003 12:38:54 +0100 [thread overview]
Message-ID: <1072697933.5223.15.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20031229032759.26802292.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
>
> Thus leaving me even-more-confused-than-usual. Ho hum.
>
> Was your fix equivalent to this patch?
not fully (looking waay back into kernel rpms ....)... the one I had was
a bit simpler in concept so this one might actually work better.
Also the problem wasn't "it doesn't work at all" it was "this ONE pci
slot isn't visible" which is why it going wrong escaped QA....
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-29 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 11:02 i450nx-scanning-fix.patch Andrew Morton
2003-12-29 11:24 ` i450nx-scanning-fix.patch Arjan van de Ven
2003-12-29 11:27 ` i450nx-scanning-fix.patch Andrew Morton
2003-12-29 11:38 ` Arjan van de Ven [this message]
2003-12-29 12:28 ` i450nx-scanning-fix.patch Matthew Wilcox
2003-12-30 19:18 ` i450nx-scanning-fix.patch Grant Grundler
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=1072697933.5223.15.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@debian.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