From: Huacai Chen <chenhuacai@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Yinbo Zhu <zhuyinbo@loongson.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>,
loongson-kernel@lists.loongnix.cn, Liu Yun <liuyun@loongson.cn>,
kernel@xen0n.name
Subject: Re: [PATCH v5 0/2] soc: loongson2_pm: add power management support
Date: Fri, 28 Jul 2023 17:48:29 +0800 [thread overview]
Message-ID: <CAAhV-H5cfGZLvThzu_mBOphGJeUSFAu_4nZvGNFJqF5++DN2OA@mail.gmail.com> (raw)
In-Reply-To: <20230728-cornball-preacher-a7e4644fcbef@wendy>
Hi, Conor, Arnd,
On Fri, Jul 28, 2023 at 4:44 PM Conor Dooley <conor.dooley@microchip.com> wrote:
>
> Hey,
>
> +CC Huacai & WANG.
>
> On Fri, Jul 28, 2023 at 03:49:42PM +0800, Yinbo Zhu wrote:
> > Loongson-2 platform support Power Management Controller (ACPI) and this
> > series patch was to add PM driver that base on dts and PM binding support.
> >
> > Change in v5:
> > 1. The patch "[PATCH v3 1/3] loongarch: export some arch-specific
> > pm interfaces" had been merged into linux-next tree thus this
> > v4 series patch need drop it and need depend on it and it's
> > patch link was:
> > https://lore.kernel.org/all/20230615091757.24686-2-zhuyinbo@loongson.cn/
>
> Just to note, it might be in linux-next, but more importantly it is also
> in v6.5-rc1, so there is no issue with dependencies.
>
> > 2. Swap the positions of compatible for 2k1000 and 2k0500.
>
> I noticed you sent a mail pinging the v4 of this series yesterday as it
> had not been picked up. Who do you actually expect to apply these
> patches? There does not appear to be a maintainer listed for the
> drivers/soc/loongson directory, just one for your GUTS driver.
>
> As a result, patches like
> <https://lore.kernel.org/all/a69170cb55cfc73e378b40ccf1d9c16f@208suo.com/>
> have gone ignored. Granted, that patch is probably crap that does not
> apply, due to 208suo.com people sending corrupted patches, but you the
> point.
>
> More interestingly there is also
> <https://lore.kernel.org/all/40b324af-3483-4b3d-b65a-a97944aa4a70@app.fastmail.com/>
> which seems to have also gone missing (I don't see it in linux-next),
> despite some discussion about how the patch should be merged.
>
> Looks to me like drivers/soc/loongson/ needs someone to take
> responsibility for picking up patches for the directory & sending them
> to the soc maintainers (with a new MAINTAINERS entry reflecting that) so
> that patches don't fall through the cracks.
As discussed when the guts driver gets merged, I think it is better to
go via Arnd's soc tree for these patches under drivers/soc/loongson/.
To Krzysztof,
I'm very sorry for the disclaimer, I will remove it, and please take it easy.
Huacai
>
> Thanks,
> Conor.
next prev parent reply other threads:[~2023-07-28 9:48 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
2023-07-28 10:21 ` Krzysztof Kozlowski
2023-07-28 8:43 ` Conor Dooley
2023-07-28 9:48 ` Huacai Chen [this message]
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=CAAhV-H5cfGZLvThzu_mBOphGJeUSFAu_4nZvGNFJqF5++DN2OA@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@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).