From: Bastien Nocera <hadess@hadess.net>
To: Hans de Goede <hdegoede@redhat.com>,
Mark Pearson <markpearson@lenovo.com>
Cc: dvhart@infradead.org, mgross@linux.intel.com,
mario.limonciello@dell.com, eliadevito@gmail.com,
bberg@redhat.com, linux-pm@vger.kernel.org,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH] Documentation: Add documentation for new platform_profile sysfs attribute
Date: Thu, 29 Oct 2020 15:21:43 +0100 [thread overview]
Message-ID: <fb95dc5b8d9cee5a66759adc268e284cb1f1a3bd.camel@hadess.net> (raw)
In-Reply-To: <ebeec472-3310-c560-e8bf-2b33c480333b@redhat.com>
On Thu, 2020-10-29 at 10:46 +0100, Hans de Goede wrote:
> <
> <snip>
> IMHO it does not belong in the sysfs API docs for the
> platform_profile
> stuff. But I guess it would be good to document it somewhere in some
> generic syfs API rules/expectations document (with a note that their
> might be exceptions).
>
> Ideally we would already have such a file somewhere, but I don't know
> if we do (I did not look). So if you feel like it (and such a file
> does
> not exist yet) then I guess a patch adding such a doc file would be
> good.
I don't know enough about the helpers and the code around it to know
whether documenting this would be needed, but I'm fine with knowing
that we're not breaking new ground here.
next prev parent reply other threads:[~2020-10-29 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 16:42 [PATCH] Documentation: Add documentation for new platform_profile sysfs attribute Mark Pearson
2020-10-27 18:11 ` Elia Devito
2020-10-28 11:54 ` Hans de Goede
2020-10-28 13:45 ` Bastien Nocera
2020-10-28 17:23 ` Hans de Goede
2020-10-29 0:55 ` [External] " Mark Pearson
2020-10-29 9:46 ` Hans de Goede
2020-10-29 14:21 ` Bastien Nocera [this message]
2020-10-29 12:33 ` Bastien Nocera
2020-10-29 11:25 ` Rafael J. Wysocki
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=fb95dc5b8d9cee5a66759adc268e284cb1f1a3bd.camel@hadess.net \
--to=hadess@hadess.net \
--cc=bberg@redhat.com \
--cc=dvhart@infradead.org \
--cc=eliadevito@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=markpearson@lenovo.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.