From: Richard Tresidder <rtresidd@electromag.com.au>
To: David Lechner <david@lechnology.com>,
sre@kernel.org, enric.balletbo@collabora.com,
ncrews@chromium.org, andrew.smirnov@gmail.com,
groeck@chromium.org, tglx@linutronix.de,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] power/supply/powersupply_sysfs: Add of_node name to uevent message if available
Date: Fri, 26 Jul 2019 10:40:28 +0800 [thread overview]
Message-ID: <3c372ca4-373d-9c03-8636-a9f065eed577@electromag.com.au> (raw)
In-Reply-To: <9a10b934-e7f3-c95f-6250-8a857bdfa912@lechnology.com>
Hi David
That it would be. I wasn't aware of that call.
I'll give it a crack and send in a new version of the patch.
Cheers
Richard Tresidder
Richard Tresidder
On 25/07/2019 10:08 pm, David Lechner wrote:
> On 7/25/19 2:47 AM, Richard Tresidder wrote:
>> If the of_node name of the supply is available from the devicetree
>> binding
>> then include it under the var POWER_SUPPLY_OF_NODE_NAME.
>> This helps where a consistent name is known via the device tree binding
>> but it is hard to identify based on the usual enumeration process.
>>
>
> Would it be possible to use of_device_uevent() instead of introducing
> a new
> property?
>
>
>
next prev parent reply other threads:[~2019-07-26 2:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 7:47 [PATCH 1/1] power/supply/powersupply_sysfs: Add of_node name to uevent message if available Richard Tresidder
2019-07-25 14:08 ` David Lechner
2019-07-26 2:40 ` Richard Tresidder [this message]
2019-07-26 4:51 ` Richard Tresidder
2019-07-26 9:43 ` Richard Tresidder
2019-07-26 20:45 ` kbuild test robot
2019-07-29 8:32 ` kbuild test robot
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=3c372ca4-373d-9c03-8636-a9f065eed577@electromag.com.au \
--to=rtresidd@electromag.com.au \
--cc=andrew.smirnov@gmail.com \
--cc=david@lechnology.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ncrews@chromium.org \
--cc=sre@kernel.org \
--cc=tglx@linutronix.de \
/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).