From: Dmitry Osipenko <digetx@gmail.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Cc: lukasz.luba@arm.com, enric.balletbo@collabora.com,
hl@rock-chips.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, abel.vesa@nxp.com, k.konieczny@samsung.com,
b.zolnierkie@samsung.com, chanwoo@kernel.org,
myungjoo.ham@samsung.com, kyungmin.park@samsung.com
Subject: Re: [PATCH v4 2/2] PM / devfreq: Add governor attribute flag for specifc sysfs nodes
Date: Thu, 22 Oct 2020 05:30:27 +0300 [thread overview]
Message-ID: <b94b5c9d-6bfc-0535-baaf-d0809f74de42@gmail.com> (raw)
In-Reply-To: <20201020030407.21047-3-cw00.choi@samsung.com>
20.10.2020 06:04, Chanwoo Choi пишет:
> /**
> * struct devfreq_governor - Devfreq policy governor
> * @node: list node - contains registered devfreq governors
> * @name: Governor's name
> + * @attr: Governor's sysfs attribute flag
> * @flags: Governor's feature flags
> * @get_target_freq: Returns desired operating frequency for the device.
> * Basically, get_target_freq will run
> @@ -57,6 +68,7 @@ struct devfreq_governor {
> struct list_head node;
>
> const char name[DEVFREQ_NAME_LEN];
> + const u64 attr;
> const u64 flags;
What about to use plural for the "attrs" as well?
next prev parent reply other threads:[~2020-10-22 2:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201020025045epcas1p2aaf684cb1bec4a390cdede45cd1eae85@epcas1p2.samsung.com>
2020-10-20 3:04 ` [PATCH v4 0/2] PM / devfreq: Add governor feature and attribute flag Chanwoo Choi
2020-10-20 3:04 ` [PATCH v4 1/2] PM / devfreq: Add governor feature flag Chanwoo Choi
2020-10-20 3:04 ` [PATCH v4 2/2] PM / devfreq: Add governor attribute flag for specifc sysfs nodes Chanwoo Choi
2020-10-22 2:30 ` Dmitry Osipenko
2020-10-22 2:47 ` Chanwoo Choi
2020-10-22 2:30 ` Dmitry Osipenko [this message]
2020-10-22 2:45 ` Chanwoo Choi
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=b94b5c9d-6bfc-0535-baaf-d0809f74de42@gmail.com \
--to=digetx@gmail.com \
--cc=abel.vesa@nxp.com \
--cc=b.zolnierkie@samsung.com \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=enric.balletbo@collabora.com \
--cc=hl@rock-chips.com \
--cc=jonathanh@nvidia.com \
--cc=k.konieczny@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=thierry.reding@gmail.com \
/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