From: "David S. Miller" <davem@redhat.com>
To: davidm@hpl.hp.com, davidm@napali.hpl.hp.com
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: qla1280 mem-mapped I/O fix
Date: Sat, 10 May 2003 05:12:33 -0700 (PDT) [thread overview]
Message-ID: <20030510.051233.112594579.davem@redhat.com> (raw)
In-Reply-To: <16060.58322.808144.819886@napali.hpl.hp.com>
From: David Mosberger <davidm@napali.hpl.hp.com>
Date: Sat, 10 May 2003 04:34:42 -0700
>>>>> On 10 May 2003 04:30:11 -0700, "David S. Miller" <davem@redhat.com> said:
DaveM> David, you absolute MAY NOT pass this:
Me? It's the driver that's doing it! ;-)
It won't do it until your changes :-)
prev parent reply other threads:[~2003-05-10 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 9:51 qla1280 mem-mapped I/O fix David Mosberger
2003-05-10 10:15 ` Arjan van de Ven
2003-05-10 10:25 ` David Mosberger
2003-05-15 15:52 ` Jes Sorensen
2003-05-16 4:06 ` Andrey Panin
2003-05-10 11:30 ` David S. Miller
2003-05-10 11:34 ` David Mosberger
2003-05-10 12:12 ` David S. Miller [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=20030510.051233.112594579.davem@redhat.com \
--to=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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