From: Marek Behun <marek.behun@nic.cz>
To: Pavel Machek <pavel@ucw.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org,
Jacek Anaszewski <jacek.anaszewski@gmail.com>
Subject: Re: kernfs: can read/write method grow buffer size?
Date: Fri, 29 Mar 2019 09:48:23 +0100 [thread overview]
Message-ID: <20190329094823.426d7ed8@nic.cz> (raw)
In-Reply-To: <20190329083440.GA12945@amd>
> pavel@amd:~/cip$ cat /sys/power/state
> freeze mem disk
> pavel@amd:~/cip$ cat /sys/class/leds/phy0-led/trigger
> none bluetooth-power rfkill-any rfkill-none kbd-scrolllock kbd-numlock
> kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock
> kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock
> AC-online BAT0-charging-or-full BAT0-charging BAT0-full
> BAT0-charging-blink-full-solid rfkill0 phy0rx phy0tx phy0assoc
> phy0radio [phy0tpt] mmc0 timer heartbeat audio-mute audio-micmute
> rfkill1 hci0-power rfkill8
> pavel@amd:~/cip$
>
Yes, and cpufreq governors too list available governosrs as space
separated list.
Maybe the "one value per file" rule was thought-of only after these
were merged?
Marek
next prev parent reply other threads:[~2019-03-29 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 3:09 kernfs: can read/write method grow buffer size? Marek Behun
2019-03-29 6:22 ` Greg Kroah-Hartman
2019-03-29 6:51 ` Marek Behun
2019-03-29 6:58 ` Greg Kroah-Hartman
2019-03-29 8:34 ` Pavel Machek
2019-03-29 8:48 ` Marek Behun [this message]
2019-03-29 10:24 ` Greg Kroah-Hartman
2019-03-29 10:26 ` Greg Kroah-Hartman
2019-03-29 10:38 ` Pavel Machek
2019-03-29 10:32 ` Pavel Machek
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=20190329094823.426d7ed8@nic.cz \
--to=marek.behun@nic.cz \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tj@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