From: Florian Fainelli <f.fainelli@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org
Cc: Markus Mayer <mmayer@broadcom.com>,
"maintainer:BROADCOM STB AVS TMON DRIVER"
<bcm-kernel-feedback-list@broadcom.com>,
Zhang Rui <rui.zhang@intel.com>, Amit Kucheria <amitk@kernel.org>,
"open list:BROADCOM STB AVS TMON DRIVER"
<linux-pm@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] thermal: brcmstb_thermal: Interrupt is optional
Date: Tue, 1 Mar 2022 13:20:27 -0800 [thread overview]
Message-ID: <f5af24df-ceca-16ca-af85-38435130a9de@gmail.com> (raw)
In-Reply-To: <f6f61340-24b1-770e-6b8d-9b47218a87be@linaro.org>
On 3/1/2022 12:47 PM, Daniel Lezcano wrote:
> On 01/03/2022 19:05, Florian Fainelli wrote:
>>
>>
>> On 9/17/2021 12:51 AM, Daniel Lezcano wrote:
>>>
>>> Applied, thanks
>>
>> Was it applied? I still cannot find it in linux-next or Linus' tree.
> I thought it was :/
No worries, I just resent it:
https://lore.kernel.org/lkml/20220301181412.2008044-1-f.fainelli@gmail.com/
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org
Cc: Markus Mayer <mmayer@broadcom.com>,
"maintainer:BROADCOM STB AVS TMON DRIVER"
<bcm-kernel-feedback-list@broadcom.com>,
Zhang Rui <rui.zhang@intel.com>, Amit Kucheria <amitk@kernel.org>,
"open list:BROADCOM STB AVS TMON DRIVER"
<linux-pm@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] thermal: brcmstb_thermal: Interrupt is optional
Date: Tue, 1 Mar 2022 13:20:27 -0800 [thread overview]
Message-ID: <f5af24df-ceca-16ca-af85-38435130a9de@gmail.com> (raw)
In-Reply-To: <f6f61340-24b1-770e-6b8d-9b47218a87be@linaro.org>
On 3/1/2022 12:47 PM, Daniel Lezcano wrote:
> On 01/03/2022 19:05, Florian Fainelli wrote:
>>
>>
>> On 9/17/2021 12:51 AM, Daniel Lezcano wrote:
>>>
>>> Applied, thanks
>>
>> Was it applied? I still cannot find it in linux-next or Linus' tree.
> I thought it was :/
No worries, I just resent it:
https://lore.kernel.org/lkml/20220301181412.2008044-1-f.fainelli@gmail.com/
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-01 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 21:36 [PATCH] thermal: brcmstb_thermal: Interrupt is optional Florian Fainelli
2021-04-26 21:36 ` Florian Fainelli
2021-09-16 0:05 ` Florian Fainelli
2021-09-16 0:05 ` Florian Fainelli
2021-09-17 7:51 ` Daniel Lezcano
2021-09-17 7:51 ` Daniel Lezcano
2022-03-01 18:05 ` Florian Fainelli
2022-03-01 18:05 ` Florian Fainelli
2022-03-01 20:47 ` Daniel Lezcano
2022-03-01 20:47 ` Daniel Lezcano
2022-03-01 21:20 ` Florian Fainelli [this message]
2022-03-01 21:20 ` Florian Fainelli
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=f5af24df-ceca-16ca-af85-38435130a9de@gmail.com \
--to=f.fainelli@gmail.com \
--cc=amitk@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mmayer@broadcom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.