From: Jonathan Corbet <corbet@lwn.net>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] sysfs.txt: add note on available attribute macros
Date: Sun, 17 Feb 2019 15:53:19 -0700 [thread overview]
Message-ID: <20190217155319.7686ce91@lwn.net> (raw)
In-Reply-To: <1550215788-19883-1-git-send-email-hofrat@osadl.org>
On Fri, 15 Feb 2019 08:29:48 +0100
Nicholas Mc Guire <hofrat@osadl.org> wrote:
> The common cases of attributes wrappers should probably be using the
> __ATTR_XXX macros to make code more concise and readable but the current
> sysfs.txt does not point developers to those convenience macros. Further
> there is no note in sysfs.txt currently explaining why trying to set a
> sysfs file to mode 0666 will fail respectively revert to 0664.
>
> Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
I've applied this, thanks.
jon
prev parent reply other threads:[~2019-02-17 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 7:29 [PATCH V2] sysfs.txt: add note on available attribute macros Nicholas Mc Guire
2019-02-17 22:53 ` Jonathan Corbet [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=20190217155319.7686ce91@lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hofrat@osadl.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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).