From: Conor Dooley <conor.dooley@microchip.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: 陈华才 <chenhuacai@loongson.cn>,
loongson-kernel@lists.loongnix.cn,
"Arnd Bergmann" <arnd@arndb.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Jianmin Lv" <lvjianmin@loongson.cn>,
wanghongliang@loongson.cn, "Liu Peibao" <liupeibao@loongson.cn>,
"Yinbo Zhu" <zhuyinbo@loongson.cn>,
"Liu Yun" <liuyun@loongson.cn>
Subject: Re: [PATCH v5 0/2] soc: loongson2_pm: add power management support
Date: Fri, 28 Jul 2023 11:14:14 +0100 [thread overview]
Message-ID: <20230728-overview-suitor-b54b5f27389f@wendy> (raw)
In-Reply-To: <7986a634-63b2-28d6-5f17-7b982ae56bcf@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
On Fri, Jul 28, 2023 at 11:45:48AM +0200, Krzysztof Kozlowski wrote:
> On 28/07/2023 11:18, Conor Dooley wrote:
> > On Fri, Jul 28, 2023 at 10:36:42AM +0200, Krzysztof Kozlowski wrote:
> >> Are we intended person/entities to receive your Reviewed-by tag?
> >
> > It's okay, you only got a "Reviewd-by" tag ;)
>
> I guess so, especially that this disclaimer should be useless. But on
> the other hand, do I want to deal with it if once Loongson sends me
> Cease-and-desist letter for something? Why even thinking about this
> should be my problem? Why should I even consider this topic: is it
> harmless or is there any risk?
Oh for sure complain. My corp email is not in the CC, but it arrived in
my inbox there...
I was just noting that the tag was not correctly provided in the first
place.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-07-28 10:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 7:49 [PATCH v5 0/2] soc: loongson2_pm: add power management support Yinbo Zhu
2023-07-28 7:49 ` [PATCH v5 1/2] soc: dt-bindings: add loongson-2 pm Yinbo Zhu
2023-07-28 7:49 ` [PATCH v5 2/2] soc: loongson2_pm: add power management support Yinbo Zhu
2023-07-28 10:46 ` Arnd Bergmann
2023-07-31 3:12 ` Yinbo Zhu
2023-07-28 12:17 ` Randy Dunlap
2023-07-31 3:14 ` Yinbo Zhu
2023-07-28 8:27 ` [PATCH v5 0/2] " 陈华才
2023-07-28 8:36 ` Krzysztof Kozlowski
2023-07-28 9:18 ` Conor Dooley
2023-07-28 9:45 ` Krzysztof Kozlowski
2023-07-28 10:14 ` Conor Dooley [this message]
2023-07-28 10:21 ` Krzysztof Kozlowski
2023-07-28 8:43 ` Conor Dooley
2023-07-28 9:48 ` Huacai Chen
2023-07-28 10:18 ` Conor Dooley
2023-07-31 14:13 ` Huacai Chen
2023-07-31 19:28 ` Arnd Bergmann
2023-08-01 8:16 ` Conor Dooley
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=20230728-overview-suitor-b54b5f27389f@wendy \
--to=conor.dooley@microchip.com \
--cc=arnd@arndb.de \
--cc=chenhuacai@loongson.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=liuyun@loongson.cn \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=lvjianmin@loongson.cn \
--cc=robh+dt@kernel.org \
--cc=wanghongliang@loongson.cn \
--cc=zhuyinbo@loongson.cn \
/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).