i2c: Use the __ATTR macro where possible
Signed-off-by: Jean Delvare <khali@linux-fr.org>
This commit is contained in:
parent
438d6c2c01
commit
7b77d065d1
@ -128,14 +128,11 @@ static ssize_t show_client_name(struct device *dev, struct device_attribute *att
|
|||||||
}
|
}
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* We can't use the DEVICE_ATTR() macro here as we want the same filename for a
|
* We can't use the DEVICE_ATTR() macro here, as we used the same name for
|
||||||
* different type of a device. So beware if the DEVICE_ATTR() macro ever
|
* an i2c adapter attribute (above).
|
||||||
* changes, this definition will also have to change.
|
|
||||||
*/
|
*/
|
||||||
static struct device_attribute dev_attr_client_name = {
|
static struct device_attribute dev_attr_client_name =
|
||||||
.attr = {.name = "name", .mode = S_IRUGO, .owner = THIS_MODULE },
|
__ATTR(name, S_IRUGO, &show_client_name, NULL);
|
||||||
.show = &show_client_name,
|
|
||||||
};
|
|
||||||
|
|
||||||
|
|
||||||
/* ---------------------------------------------------
|
/* ---------------------------------------------------
|
||||||
|
Loading…
Reference in New Issue
Block a user