From: Jeff Garzik <jeff@garzik.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de, akpm@osdl.org,
bcasavan@sgi.com
Subject: Re: [PATCH] PCI: Move various PCI IDs to header file
Date: Thu, 22 Jun 2006 22:02:29 -0400 [thread overview]
Message-ID: <449B4BB5.4080105@garzik.org> (raw)
In-Reply-To: <20060622185142.c8bc1b16.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> lkml is like a "melting pot."
It's also easy to miss stuff, which is why Andrew manages to CC the
relevant maintainers, when something pops into his tree...
Jeff
next prev parent reply other threads:[~2006-06-23 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606222300.k5MN0uPW000741@hera.kernel.org>
2006-06-23 1:29 ` [PATCH] PCI: Move various PCI IDs to header file Jeff Garzik
2006-06-23 1:51 ` Randy.Dunlap
2006-06-23 2:02 ` Jeff Garzik [this message]
2006-07-05 15:55 ` Brent Casavant
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=449B4BB5.4080105@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=bcasavan@sgi.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.