From: Martin Dalecki <dalecki@evision-ventures.com>
To: Greg KH <greg@kroah.com>
Cc: Patrick Mochel <mochel@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: device model documentation 1/3
Date: Tue, 04 Jun 2002 18:00:26 +0200 [thread overview]
Message-ID: <3CFCE41A.4030005@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206040904430.654-100000@geena.pdx.osdl.net> <3CFCE09B.6090007@evision-ventures.com> <20020604165345.GB28805@kroah.com>
Greg KH wrote:
> On Tue, Jun 04, 2002 at 05:45:31PM +0200, Martin Dalecki wrote:
>
>>Patrick Mochel wrote:
>>
>>
>>>Bus Types
>>>
>>>struct bus_type {
>>
>>...
>>
>>
>>
>>> int (*bind) (struct device * dev, struct device_driver *
>>> drv);
>>>};
>>>
>>
>>Please - Why do you call it bind? Does it have something with
>>netowrking to do? Please just name it attach. This way the old UNIX
>>guys among us won't have to drag a too big
>>"UNIX to Linux translation dictionary" around with them.
>>As an "added bonus" you will stay consistent with -
>>
>>USB code base in kernel
>
>
> Huh? The usb code base doesn't use either "bind" or "attach" in it's
> api.
>
> And who cares? You knew what he ment by this, and it's a pretty
> standard term.
I care. And I had to thing long and hard before guessing what it could
be. (I noticed this nomenclature error already in the kernel patch.)
next prev parent reply other threads:[~2002-06-04 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 16:25 device model documentation 1/3 Patrick Mochel
2002-06-04 15:45 ` Martin Dalecki
2002-06-04 16:53 ` Greg KH
2002-06-04 16:00 ` Martin Dalecki [this message]
2002-06-04 17:40 ` Patrick Mochel
2002-06-04 18:26 ` Patrick Mochel
2002-06-04 19:06 ` Adam Kropelin
2002-06-05 9:08 ` Martin Dalecki
2002-06-05 8:36 ` Martin Dalecki
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=3CFCE41A.4030005@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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