Linux Power Management development
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>, linux-pm@vger.kernel.org
Cc: Lukasz Luba <lukasz.luba@arm.com>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust entry in THERMAL/POWER_ALLOCATOR after header movement
Date: Sat, 1 Apr 2023 21:26:30 +0200	[thread overview]
Message-ID: <7aafa534-412d-d7b9-96f6-d5cef98c8021@linaro.org> (raw)
In-Reply-To: <20230328091737.6785-1-lukas.bulwahn@gmail.com>

On 28/03/2023 11:17, Lukas Bulwahn wrote:
> Commit e97b6e04095a ("thermal/core: Relocate the traces definition in
> thermal directory") moves include/trace/events/thermal_power_allocator.h to
> drivers/thermal/thermal_trace_ipa.h, but misses to adjust the file entry
> for the THERMAL/POWER_ALLOCATOR section.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
> 
> Adjust this file entry in THERMAL/POWER_ALLOCATOR.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Daniel, please apply this minor clean-up patch on top of the commit above. Thanks.

Applied, thanks

-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


      parent reply	other threads:[~2023-04-01 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  9:17 [PATCH] MAINTAINERS: adjust entry in THERMAL/POWER_ALLOCATOR after header movement Lukas Bulwahn
2023-03-28  9:24 ` Lukasz Luba
2023-04-01 19:26 ` Daniel Lezcano [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=7aafa534-412d-d7b9-96f6-d5cef98c8021@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=amitk@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.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