From: SeongJae Park <sj@kernel.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: SeongJae Park <sj@kernel.org>,
sre@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] power: supply: core: Fix a build failure due to psy_has_property() definition location
Date: Wed, 29 Sep 2021 16:15:53 +0000 [thread overview]
Message-ID: <20210929161553.26986-1-sj@kernel.org> (raw)
In-Reply-To: <YVSO1NYeegW/trvr@google.com>
On Wed, 29 Sep 2021 09:05:40 -0700 Matthias Kaehlcke <mka@chromium.org> wrote:
> Hi SeongJae,
>
> thanks for the fix!
>
> Geert sent a similar patch earlier:
>
> https://patchwork.kernel.org/project/linux-pm/patch/7b35a74f2c2ad19c8dc1ca60c59e48a14288677f.1632830348.git.geert+renesas@glider.be/
No problem, good to hear that!
Thanks,
SJ
[...]
prev parent reply other threads:[~2021-09-29 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 13:02 [PATCH] power: supply: core: Fix a build failure due to psy_has_property() definition location SeongJae Park
2021-09-29 16:05 ` Matthias Kaehlcke
2021-09-29 16:15 ` SeongJae Park [this message]
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=20210929161553.26986-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=sre@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