From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] netdev - udevdb+dev.d changes
Date: Thu, 01 Apr 2004 00:22:30 +0000 [thread overview]
Message-ID: <20040401002230.GA13761@kroah.com> (raw)
In-Reply-To: <20040328184840.GA5877@vrfy.org>
On Thu, Apr 01, 2004 at 01:40:26AM +0200, Kay Sievers wrote:
> > > o We now only add a device to the db, if we have successfully created
> > > the main node or successfully renamed a netdev. This is the main part
> > > of the patch, cause I needed to clean the retval passing trough all
> > > the functions used for node creation.
> > >
> > > o DEVNODE sounds a bit ugly for netdev's so I exported DEVNAME too.
> > > Can we change the name?
> >
> > Can you think of a better name?
>
> I think DEVNAME sounds better for a netdev and is fine for a node too?
> What do you think?
That's what I originally had, yet changed it to DEVNODE. But now that
we have network device support, it makes more sense to call it that.
Care to make a patch that does that too?
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-04-01 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 18:48 [PATCH] netdev - udevdb+dev.d changes Kay Sievers
2004-03-31 23:14 ` Greg KH
2004-03-31 23:40 ` Kay Sievers
2004-04-01 0:22 ` Greg KH [this message]
2004-04-01 0:41 ` Kay Sievers
2004-04-01 1:02 ` Greg KH
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=20040401002230.GA13761@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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.