From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: Denis Efremov <efremov@linux.com>,
Julia Lawall <julia.lawall@inria.fr>,
Alex Dewar <alex.dewar90@gmail.com>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH V3 1/8] sysfs: Add sysfs_emit and sysfs_emit_at to format sysfs output
Date: Wed, 30 Sep 2020 06:58:53 -0700 [thread overview]
Message-ID: <1a9cac491e1813b94cde3bed67d642f52cd81e7d.camel@perches.com> (raw)
In-Reply-To: <20200930115740.GA1611809@kroah.com>
On Wed, 2020-09-30 at 13:57 +0200, Greg Kroah-Hartman wrote:
> Kees, and Rafael, I don't know if you saw this proposal from Joe for
> sysfs files, questions below:
https://lore.kernel.org/linux-pm/5d606519698ce4c8f1203a2b35797d8254c6050a.1600285923.git.joe@perches.com/T/
> So I guess I'm asking for another developer to at least agree that this
> feels like the right way forward here. I don't want to start down this
> path, only to roll them all back as it feels like pointless churn.
https://lore.kernel.org/lkml/c256eba42a564c01a8e470320475d46f@AcuMS.aculab.com/T/#mb40d265bc1dabb8bb64b0dfa29dd8eda44be056e
next prev parent reply other threads:[~2020-09-30 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 20:40 [PATCH V3 0/8] sysfs: drivers core: Add and use sysfs_emit and sysfs_emit_at Joe Perches
2020-09-16 20:40 ` [PATCH V3 1/8] sysfs: Add sysfs_emit and sysfs_emit_at to format sysfs output Joe Perches
2020-09-30 11:57 ` Greg Kroah-Hartman
2020-09-30 13:58 ` Joe Perches [this message]
2020-10-02 11:25 ` Greg Kroah-Hartman
2020-10-01 4:17 ` Kees Cook
2020-10-01 4:22 ` Joe Perches
2020-10-02 22:30 ` Kees Cook
2020-10-03 13:55 ` Greg Kroah-Hartman
2020-10-03 14:59 ` Joe Perches
2020-10-03 22:15 ` Kees Cook
2020-10-01 20:50 ` Greg Kroah-Hartman
2020-10-02 22:27 ` Kees Cook
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=1a9cac491e1813b94cde3bed67d642f52cd81e7d.camel@perches.com \
--to=joe@perches.com \
--cc=alex.dewar90@gmail.com \
--cc=corbet@lwn.net \
--cc=efremov@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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).