s390: struct device - replace bus_id with dev_name(), dev_set_name()
Subsystems (4)
This patch is part of a larger patch series which will remove the "char bus_id[20]" name string from struct device. The device name is managed in the kobject anyway, and without any size limitation, and just needlessly copied into "struct device".
To set and read the device name dev_name(dev) and dev_set_name(dev) must be used. If your code uses static kobjects, which it shouldn't do, "const char *init_name" can be used to statically provide the name the registered device should have. At registration time, the init_name field is cleared, to enforce the use of dev_name(dev) to access the device name at a later time.
We need to get rid of all occurrences of bus_id in the entire tree to be able to enable the new interface. Please apply this patch, and possibly convert any remaining remaining occurrences of bus_id.
We want to submit a patch to -next, which will remove bus_id from "struct device", to find the remaining pieces to convert, and finally switch over to the new api, which will remove the 20 bytes array and does no longer have a size limitation.
Thanks,
Kay
From: Kay Sievers <[email protected]>
Subject: s390: struct device - replace bus_id with dev_name(), dev_set_name()
---
drivers/s390/block/dasd_devmap.c +7 -6
@@ -23,6 +23,7 @@/* This is ugly... */ #define PRINTK_HEADER "dasd_devmap:" +#define DASD_BUS_ID_SIZE 20#include "dasd_int.h"
@@ -41,7 +42,7 @@ EXPORT_SYMBOL_GPL(dasd_page_cache);*/ struct dasd_devmap {struct list_head list; -char bus_id[BUS_ID_SIZE ]; +char bus_id[DASD_BUS_ID_SIZE ];unsigned int devindex;unsigned short features;struct dasd_device *device;
@@ -94,7 +95,7 @@ dasd_hash_busid(const char *bus_id)int hash, i; hash =0 ; -for (i =0 ; (i <BUS_ID_SIZE ) && *bus_id; i++, bus_id++) +for (i =0 ; (i <DASD_BUS_ID_SIZE ) && *bus_id; i++, bus_id++) hash += *bus_id;return hash &0xff ; }
@@ -301,7 +302,7 @@ dasd_parse_range( char *parsestring ) {int from, from_id0, from_id1;int to, to_id0, to_id1;int features, rc; -char bus_id[BUS_ID_SIZE +1 ], *str; +char bus_id[DASD_BUS_ID_SIZE +1 ], *str; str = parsestring; rc =dasd_busid (&str, &from_id0, &from_id1, &from);
@@ -407,14 +408,14 @@ dasd_add_busid(const char *bus_id, int features) devmap =NULL ; hash =dasd_hash_busid (bus_id);list_for_each_entry (tmp, &dasd_hashlists[hash], list) -if (strncmp (tmp->bus_id, bus_id,BUS_ID_SIZE ) ==0 ) { +if (strncmp (tmp->bus_id, bus_id,DASD_BUS_ID_SIZE ) ==0 ) { devmap = tmp;break ; }if (!devmap) {/* This bus_id is new. */ new->devindex = dasd_max_devindex++; -strncpy (new->bus_id, bus_id,BUS_ID_SIZE ); +strncpy (new->bus_id, bus_id,DASD_BUS_ID_SIZE ); new->features = features; new->device =NULL ;list_add (&new->list, &dasd_hashlists[hash]);
@@ -439,7 +440,7 @@ dasd_find_busid(const char *bus_id) devmap =ERR_PTR (-ENODEV ); hash =dasd_hash_busid (bus_id);list_for_each_entry (tmp, &dasd_hashlists[hash], list) { -if (strncmp (tmp->bus_id, bus_id,BUS_ID_SIZE ) ==0 ) { +if (strncmp (tmp->bus_id, bus_id,DASD_BUS_ID_SIZE ) ==0 ) { devmap = tmp;break ; }
drivers/s390/block/dcssblk.c +3 -2
@@ -21,6 +21,7 @@#define DCSSBLK_NAME "dcssblk"#define DCSSBLK_MINORS_PER_DISK 1#define DCSSBLK_PARM_LEN 400 +#define DCSS_BUS_ID_SIZE 20#ifdef DCSSBLK_DEBUG #define PRINT_DEBUG(x...) printk(KERN_DEBUG DCSSBLK_NAME " debug: " x)
@@ -50,7 +51,7 @@ static struct block_device_operations dcssblk_devops = {struct dcssblk_dev_info {struct list_head lh;struct device dev; -char segment_name[BUS_ID_SIZE ]; +char segment_name[DCSS_BUS_ID_SIZE ];atomic_t use_count;struct gendisk *gd;unsigned long start;
@@ -65,7 +66,7 @@ struct dcssblk_dev_info {struct segment_info {struct list_head lh; -char segment_name[BUS_ID_SIZE ]; +char segment_name[DCSS_BUS_ID_SIZE ];unsigned long start;unsigned long end;int segment_type;
drivers/s390/cio/ccwgroup.c +5 -3
@@ -19,6 +19,8 @@#include <asm/ccwdev.h> #include <asm/ccwgroup.h> +#define CCW_BUS_ID_SIZE 20 +/* In Linux 2.4, we had a channel device layer called "chandev" * that did all sorts of obscure stuff for networking devices. * This is another driver that serves as a replacement for just
@@ -172,7 +174,7 @@ static int __get_next_bus_id(const char **buf, char *bus_id) len = end - start +1 ; end++; } -if (len <BUS_ID_SIZE ) { +if (len <CCW_BUS_ID_SIZE ) {strlcpy (bus_id, start, len); rc =0 ; }else
@@ -181,7 +183,7 @@ static int __get_next_bus_id(const char **buf, char *bus_id)return rc; } -static int __is_valid_bus_id (char bus_id[BUS_ID_SIZE ]) +static int __is_valid_bus_id (char bus_id[CCW_BUS_ID_SIZE ]) {int cssid, ssid, devno;
@@ -213,7 +215,7 @@ int ccwgroup_create_from_string(struct device *root, unsigned int creator_id, {struct ccwgroup_device *gdev;int rc, i; -char tmp_bus_id[BUS_ID_SIZE ]; +char tmp_bus_id[CCW_BUS_ID_SIZE ];const char *curr_buf; gdev = kzalloc(sizeof(*gdev) + num_devices * sizeof(gdev->cdev[0]),
drivers/s390/cio/device.c +1 -1
@@ -1719,7 +1719,7 @@ __ccwdev_check_busid(struct device *dev, void *id) bus_id = id; -return (strncmp (bus_id,dev_name (dev),BUS_ID_SIZE ) ==0 ); +return (strcmp (bus_id,dev_name (dev)) ==0 ); }
drivers/s390/scsi/zfcp_aux.c +4 -2
@@ -28,6 +28,8 @@#include <linux/miscdevice.h> #include "zfcp_ext.h" +#define ZFCP_BUS_ID_SIZE 20 +static char *device;MODULE_AUTHOR ("IBM Deutschland Entwicklung GmbH - [email protected]" );
@@ -83,9 +85,9 @@ static int __init zfcp_device_setup(char *devstr)strcpy (str, devstr); token =strsep (&str,"," ); -if (!token ||strlen (token) >=BUS_ID_SIZE ) +if (!token ||strlen (token) >=ZFCP_BUS_ID_SIZE ) goto err_out; -strncpy (zfcp_data.init_busid, token,BUS_ID_SIZE ); +strncpy (zfcp_data.init_busid, token,ZFCP_BUS_ID_SIZE ); token =strsep (&str,"," ); if (!token || strict_strtoull(token, 0,
Quoted 7 lines · Kay Sievers
From: Kay Sievers <[email protected]>
Subject: s390: struct device - replacebus_idwithdev_name(),dev_set_name()Cc Martin Schwidefsky <[email protected]>Cc Cornelia Huck <[email protected]>Signed-off-by Kay Sievers <[email protected]>
Other than the fact that this patch is a bit mis-named (it just gets rid of BUS_ID_SIZE), this looks fine to me.
Quoted 6 lines · Cornelia Huck
Quoted 3 lines · Kay Sievers
From: Kay Sievers <[email protected]>
Subject: s390: struct device - replacebus_idwithdev_name(),dev_set_name()
Quoted 7 lines
Quoted 4 lines
Cc Martin Schwidefsky <[email protected]>Cc Cornelia Huck <[email protected]>Signed-off-by Kay Sievers <[email protected]>Other than the fact that this patch is a bit mis-named (it just gets rid of
BUS_ID_SIZE), this looks fine to me.
Who is supposed to send this upstream and when?
Quoted 7 lines · Heiko Carstens
Quoted 6 lines · Cornelia Huck
Quoted 3 lines · Kay Sievers
From: Kay Sievers <[email protected]>
Subject: s390: struct device - replacebus_idwithdev_name(),dev_set_name()
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Cc Martin Schwidefsky <[email protected]>Cc Cornelia Huck <[email protected]>Signed-off-by Kay Sievers <[email protected]>Other than the fact that this patch is a bit mis-named (it just gets rid of
BUS_ID_SIZE), this looks fine to me.
Yeah, sorry, it's one of the 49 patches, where the subjects isn't right, because you did the conversion already. :)
Quoted 1 line
Who is supposed to send this upstream and when?
Would be fine if it goes through the s390 tree, and gets merged there soon so it shows up in -next.
Thanks,
Kay
Quoted 16 lines · Kay Sievers
Quoted 7 lines · Heiko Carstens
Quoted 6 lines · Cornelia Huck
Quoted 3 lines · Kay Sievers
From: Kay Sievers <[email protected]>
Subject: s390: struct device - replacebus_idwithdev_name(),dev_set_name()Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Cc Martin Schwidefsky <[email protected]>Cc Cornelia Huck <[email protected]>Signed-off-by Kay Sievers <[email protected]>Other than the fact that this patch is a bit mis-named (it just gets rid of
BUS_ID_SIZE), this looks fine to me.
Quoted 7 lines
Yeah, sorry, it's one of the 49 patches, where the subjects isn't right, because you did the conversion already. :)
Quoted 1 line
Who is supposed to send this upstream and when?
Would be fine if it goes through the s390 tree, and gets merged there soon so it shows up in -next.
Just to get this right: it doesn't depend on any other patches and is fine as a standalone patch, right?
Sorry, this isn't obvious for me ;)
Quoted 20 lines · Heiko Carstens
Quoted 19 lines · Kay Sievers
Quoted 7 lines · Heiko Carstens
Quoted 6 lines · Cornelia Huck
Quoted 3 lines · Kay Sievers
From: Kay Sievers <[email protected]>
Subject: s390: struct device - replacebus_idwithdev_name(),dev_set_name()Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Cc Martin Schwidefsky <[email protected]>Cc Cornelia Huck <[email protected]>Signed-off-by Kay Sievers <[email protected]>Other than the fact that this patch is a bit mis-named (it just gets rid of
BUS_ID_SIZE), this looks fine to me.Yeah, sorry, it's one of the 49 patches, where the subjects isn't right, because you did the conversion already. :)
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
Who is supposed to send this upstream and when?
Would be fine if it goes through the s390 tree, and gets merged there soon so it shows up in -next.
Just to get this right: it doesn't depend on any other patches and is fine as a standalone patch, right?
Sorry, this isn't obvious for me ;)
The stuff it depends on, we already put into .27. It should not depend on anything not in a released version, yes.
Kay