From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Hanna Linder <hannal@us.ibm.com>
Subject: Compile breakage from me
Date: Mon, 25 Oct 2004 13:05:31 -0400 [thread overview]
Message-ID: <417D325B.8060009@pobox.com> (raw)
Argh, I thought GregKH had sent for_each_pci_dev()
Wearing a brown paper bag, can one of you please "cset -x" this changeset?
ChangeSet@1.2000.17.1, 2004-10-21 18:47:50-04:00, hannal@us.ibm.com
[PATCH] hw_random.c: replace pci_find_device
As pci_find_device is going away I've replaced it with pci_get_device.
for_each_pci_dev is a macro wrapper around pci_get_device.
If someone with this hardware could test it I would appreciate it.
next reply other threads:[~2004-10-25 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 17:05 Jeff Garzik [this message]
2004-10-25 17:13 ` Compile breakage from me Linus Torvalds
2004-10-25 17:25 ` Linus Torvalds
2004-10-25 17:43 ` Jeff Garzik
2004-10-25 20:20 ` Jeff Garzik
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=417D325B.8060009@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=hannal@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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