From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: kay.sievers@vrfy.org, greg@kroah.com
Subject: [PATCH 0/6]: Get rid of BUS_ID_SIZE in networking
Date: Tue, 26 May 2009 21:39:42 -0700 (PDT) [thread overview]
Message-ID: <20090526.213942.196879926.davem@davemloft.net> (raw)
The generic device layer got rid of it's bus name string length
limitations by moving to dynamically allocated strings for names.
But there are things all over the tree that indirectly reference the
old BUS_ID_SIZE.
I had this glorious and ambitious patch almost finished that tried to
tackle the MII_BUS_ID_SIZE thing by similarly implementing dynamic
string lengths there but I gave up. :-) It's a lot of work and I do
not have the hardware to test this, and in order to just simply build
all the effected drivers I would have to use 3 or 4 different cross
compiles. No thanks.
So most of this is in the form of either "get rid of it", "replace
with constant '20'", or "use MII_BUS_ID instead".
I'm pretty sure I got everything in the networking in net-next-2.6,
so if I missed anything let me know.
(Kay, I'll kill the sparc one in my sparc-next-2.6 tree when I
next get the chance.)
next reply other threads:[~2009-05-27 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 4:39 David Miller [this message]
2009-05-27 23:53 ` [PATCH 0/6]: Get rid of BUS_ID_SIZE in networking 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=20090526.213942.196879926.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.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 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).