From: Rex-BC Chen <rex-bc.chen@mediatek.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Jiabing Wan <wanjiabing@vivo.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"Jia-Wei Chang" <jia-wei.chang@mediatek.com>,
Andrew-sh.Cheng <andrew-sh.cheng@mediatek.com>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v2] cpufreq: mediatek: Fix potential deadlock problem in mtk_cpufreq_set_target
Date: Wed, 11 May 2022 11:23:12 +0800 [thread overview]
Message-ID: <17a0d8c02d18f99e6f29d65c17baf0281673ca07.camel@mediatek.com> (raw)
In-Reply-To: <20220511031122.kkotwq7co2vx5zqp@vireshk-i7>
On Wed, 2022-05-11 at 08:41 +0530, Viresh Kumar wrote:
> On 10-05-22, 19:23, Rex-BC Chen wrote:
> > I am not sure what's the problem.
> > But I subscribed the linux-arm-kernel mailing list and linux-
> > mediatek.
> >
> > As for LKML, do you mean subscribe "List: linux-kernel;" in [1]?
>
> Yes, this is one of the most useful email lists and mostly gets cc'd
> anyway, you
> can disable mail delivery if you don't want to get emails.
>
> I asked because I couldn't find your email in
> https://lore.kernel.org/lkml, but
> its fine either way.
>
Hello Viresh,
thanks for your suggestion.
I will try to subscribe this.
BRs,
Rex
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-11 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:05 [PATCH v2] cpufreq: mediatek: Fix potential deadlock problem in mtk_cpufreq_set_target Wan Jiabing
2022-05-10 9:12 ` Viresh Kumar
2022-05-10 9:23 ` Jiabing Wan
2022-05-10 9:28 ` Viresh Kumar
2022-05-10 9:36 ` Jiabing Wan
2022-05-10 11:23 ` Rex-BC Chen
2022-05-11 3:11 ` Viresh Kumar
2022-05-11 3:23 ` Rex-BC Chen [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=17a0d8c02d18f99e6f29d65c17baf0281673ca07.camel@mediatek.com \
--to=rex-bc.chen@mediatek.com \
--cc=andrew-sh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jia-wei.chang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=wanjiabing@vivo.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