From: Paul Sokolovsky <pmiscml@gmail.com>
To: linux-kernel@vger.kernel.org, Adrian Bunk <bunk@stusta.de>,
Greg Kroah-Hartman <gregkh@suse.de>
Cc: kernel-discuss@handhelds.org
Subject: Where did find_bus() go in 2.6.18?
Date: Mon, 20 Nov 2006 00:34:37 +0200 [thread overview]
Message-ID: <1154868495.20061120003437@gmail.com> (raw)
Hello linux-kernel,
We here at Handhelds.org upgrading our drivers to 2.6.18 and I just
caught a case of find_bus() being undefined during link. Quickly
traced this to
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=7e4ef085ea4b00cfc34e854edf448c729de8a0a5
But alas, the commit message is not as good as some others are, and
doesn't mention what should be used instead. So, if find_bus() is
"unused", what should be used instead?
Thank you,
--
Paul mailto:pmiscml@gmail.com
next reply other threads:[~2006-11-19 22:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 22:34 Paul Sokolovsky [this message]
2006-11-19 23:45 ` Where did find_bus() go in 2.6.18? Jiri Slaby
2006-11-20 0:12 ` Greg KH
2006-11-20 14:13 ` Re[2]: " Paul Sokolovsky
2006-11-20 17:35 ` Adrian Bunk
2006-11-21 15:08 ` Re[2]: " Paul Sokolovsky
2006-11-21 15:16 ` Arjan van de Ven
2006-11-21 18:04 ` Adrian Bunk
2006-11-21 7:54 ` Greg KH
2006-11-22 8:36 ` Re[2]: " Paul Sokolovsky
2006-11-21 19:02 ` Dmitry Torokhov
2006-11-20 0:13 ` Paul Sokolovsky
2006-11-20 8:34 ` Arjan van de Ven
2006-11-21 18:29 ` Matthew Frost
2006-11-21 19:01 ` Evgeniy Polyakov
2006-11-21 19:41 ` Re[2]: " Paul Sokolovsky
2006-11-21 20:34 ` Matthew Frost
2006-11-20 9:35 ` pHilipp Zabel
-- strict thread matches above, loose matches on Subject: below --
2006-11-21 14:15 Al Boldi
2006-11-21 14:32 ` Arjan van de Ven
2006-11-22 14:18 ` Al Boldi
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=1154868495.20061120003437@gmail.com \
--to=pmiscml@gmail.com \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=kernel-discuss@handhelds.org \
--cc=linux-kernel@vger.kernel.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 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.