From: Kay Sievers <kay.sievers@suse.de>
To: Greg KH <greg@kroah.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Takashi Iwai <tiwai@suse.de>,
"David S. Miller" <davem@davemloft.net>,
David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject:
Date: Sat, 20 Jun 2009 21:45:24 +0200 [thread overview]
Message-ID: <1245527124.30962.14.camel@yio.site> (raw)
The final piece of the driver core name limit. We are about to remove
BUS_ID_SIZE.
Some patches may still be in your queue. Just to make sure, we will
finish our task this time: David, David, James, Takashi, can you please
give an update, or take care of removing the last instances, or let me
know if you want a patch, or let us know, if we should just change it to
"20".
$ find . -name "*.[ch]" | xargs grep '[^_]BUS_ID_SIZE'
./drivers/mtd/nand/txx9ndfmc.c: char mtdname[BUS_ID_SIZE + 2];
./drivers/scsi/scsi_transport_fc.c: char bsg_name[BUS_ID_SIZE]; /*20*/
./arch/sparc/kernel/vio.c: if (strlen(bus_id_name) >= BUS_ID_SIZE - 4) {
./sound/soc/txx9/txx9aclc.c: char devname[BUS_ID_SIZE + 2];
Thanks a lot,
Kay
From: Kay Sievers <kay.sievers@vrfy.org>
Subject: Driver Core: remove BUS_ID_SIZE
The name size limit is gone from the driver-core, this is
the removal of the last left-over.
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
---
include/linux/device.h | 2 --
1 file changed, 2 deletions(-)
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -25,8 +25,6 @@
#include <asm/atomic.h>
#include <asm/device.h>
-#define BUS_ID_SIZE 20
-
struct device;
struct device_private;
struct device_driver;
next reply other threads:[~2009-06-20 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 19:45 Kay Sievers [this message]
2009-06-21 9:04 ` Takashi Iwai
2009-06-22 12:56 ` Re: David Woodhouse
2009-06-24 8:27 ` BUS_ID_SIZE is going away Kay Sievers
2009-06-24 11:14 ` David Woodhouse
2009-06-24 12:59 ` Catalin Marinas
2009-06-24 14:09 ` David Woodhouse
2009-06-24 14:20 ` Catalin Marinas
2009-06-28 11:47 ` Kay Sievers
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=1245527124.30962.14.camel@yio.site \
--to=kay.sievers@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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).