From: David Miller <davem@davemloft.net>
To: kay.sievers@vrfy.org
Cc: greg@kroah.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: net: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Mon, 10 Nov 2008 13:55:30 -0800 (PST) [thread overview]
Message-ID: <20081110.135530.55645015.davem@davemloft.net> (raw)
In-Reply-To: <1226057416.4100.18.camel@nga>
From: Kay Sievers <kay.sievers@vrfy.org>
Date: Fri, 07 Nov 2008 12:30:16 +0100
> Updated patch, which does not replace BUS_ID_SIZE for now.
>
> (BUS_ID_SIZE will go away from the driver core after the API switch, and
> it has to be replaced by a local definition in the network tree, or the
> limit can be removed entirely.)
Applied to net-next-2.6, thanks Kay.
next prev parent reply other threads:[~2008-11-10 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 1:14 net: struct device - replace bus_id with dev_name(), dev_set_name() Kay Sievers
2008-10-30 4:33 ` Marcel Holtmann
2008-11-07 11:30 ` Kay Sievers
2008-11-10 21:55 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-25 22:52 Kay Sievers
2009-01-27 5:13 ` David Miller
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=20081110.135530.55645015.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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.