From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Rob Herring <robh+dt@kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] thermal: rcar_thermal: Use platform_get_irq_optional() to get the interrupt
Date: Wed, 9 Mar 2022 13:40:27 +0100 [thread overview]
Message-ID: <073f3d21-f544-4c75-d20b-ec7ef533e5fc@linaro.org> (raw)
In-Reply-To: <CA+V-a8uTtUjj2ccHDqB0TKfKw5KO-joPv0umw1fDP4cz6sUj2Q@mail.gmail.com>
On 09/03/2022 12:59, Lad, Prabhakar wrote:
[ ... ]
>> ---
>> drivers/thermal/rcar_thermal.c | 17 ++++++++++++-----
>> 1 file changed, 12 insertions(+), 5 deletions(-)
>>
> This patch is not in -next yet. In which release v5.18/19 do you plan
> to merge this in?
Right, I missed it, I'll try to catch it up for v5.18-rc1, may be with a
second PR.
It is in the linux-next branch now and will land in linux-next tree
--
<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
next prev parent reply other threads:[~2022-03-09 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 14:40 [PATCH v4] thermal: rcar_thermal: Use platform_get_irq_optional() to get the interrupt Lad Prabhakar
2022-01-12 8:35 ` Geert Uytterhoeven
2022-03-09 11:59 ` Lad, Prabhakar
2022-03-09 12:40 ` Daniel Lezcano [this message]
2022-03-09 12:47 ` Lad, Prabhakar
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=073f3d21-f544-4c75-d20b-ec7ef533e5fc@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=rafael@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).