From: "David S. Miller" <davem@davemloft.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: chas@cmf.nrl.navy.mil, hch@infradead.org, netdev@oss.sgi.com,
davem@redhat.com
Subject: Re: [PATCH][ATM]: [horizon] eliminate pci_find_device()
Date: Mon, 25 Oct 2004 20:22:21 -0700 [thread overview]
Message-ID: <20041025202221.4f4d32a3.davem@davemloft.net> (raw)
In-Reply-To: <20041022145235.GA19847@infradead.org>
On Fri, 22 Oct 2004 15:52:35 +0100
Christoph Hellwig <hch@infradead.org> wrote:
> On Fri, Oct 22, 2004 at 08:03:15AM -0400, chas williams (contractor) wrote:
> > In message <20041021113949.GB3720@infradead.org>,Christoph Hellwig writes:
> > >The same device list comments as for ambassador apply here aswell.
> >
> > better?
>
> yes.
Applied, thanks Chas and Christoph.
prev parent reply other threads:[~2004-10-26 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 11:28 [PATCH][ATM]: [horizon] eliminate pci_find_device() chas williams (contractor)
2004-10-21 11:39 ` Christoph Hellwig
2004-10-22 12:03 ` chas williams (contractor)
2004-10-22 14:52 ` Christoph Hellwig
2004-10-26 3:22 ` 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=20041025202221.4f4d32a3.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chas@cmf.nrl.navy.mil \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=netdev@oss.sgi.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).