From: Greg KH <greg@kroah.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: bus_type->dev_attrs not properly thought out
Date: Sat, 18 Sep 2004 08:57:31 -0700 [thread overview]
Message-ID: <20040918155731.GA24022@kroah.com> (raw)
In-Reply-To: <200409181043.42268.dtor_core@ameritech.net>
On Sat, Sep 18, 2004 at 10:43:41AM -0500, Dmitry Torokhov wrote:
> What's wrong with the following (drivers/input/serio/serio.c):
>
> static struct device_attribute serio_device_attrs[] = {
> __ATTR(description, S_IRUGO, serio_show_description, NULL),
You should use __ATTR_RO() for that one :)
> __ATTR(driver, S_IWUSR | S_IRUGO, serio_show_driver, serio_rebind_driver),
> __ATTR(bind_mode, S_IWUSR | S_IRUGO, serio_show_bind_mode, serio_set_bind_mode),
> __ATTR_NULL
> };
>
> Pretty compact and expressive IMHO.
Yes, that's the way to currently do it. Russell, is that acceptable?
thanks,
greg k-h
prev parent reply other threads:[~2004-09-18 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 14:56 bus_type->dev_attrs not properly thought out Russell King
2004-09-18 15:43 ` Dmitry Torokhov
2004-09-18 15:57 ` Greg KH [this message]
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=20040918155731.GA24022@kroah.com \
--to=greg@kroah.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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