From: Alexander Viro <viro@math.psu.edu>
To: Patrick Mochel <mochel@osdl.org>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [RFC] device_initialize()
Date: Tue, 15 Oct 2002 14:08:28 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0210151405450.10323-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0210151053040.1038-100000@cherise.pdx.osdl.net>
On Tue, 15 Oct 2002, Patrick Mochel wrote:
> Overall, I agree with the concept of the patch. I wonder though if we
> could do it without burdening all the callers of device_register() to
> first call device_initialize(). Well, tastefully at least.
I'd rather add device_add() and make device_register() call device_initialize()
followed by device_add()...
BTW, my variant of the same beast is on
ftp.math.psu.edu/pub/viro/O/O142-device_add-C42
with uses in O14[3-6]* in the same place...
prev parent reply other threads:[~2002-10-15 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 17:24 [RFC] device_initialize() Greg KH
2002-10-14 18:03 ` Greg KH
2002-10-15 17:58 ` Patrick Mochel
2002-10-15 18:08 ` Alexander Viro [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=Pine.GSO.4.21.0210151405450.10323-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mochel@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;
as well as URLs for NNTP newsgroup(s).