From: Shawn Guo <shawnguo@kernel.org>
To: Martin Kaiser <martin@kaiser.cx>
Cc: Stephen Boyd <sboyd@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Abel Vesa <abelvesa@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] ARM: imx25: print silicon revision at startup
Date: Sun, 6 Aug 2023 11:23:53 +0800 [thread overview]
Message-ID: <20230806032353.GX151430@dragon> (raw)
In-Reply-To: <20230802183849.2gzlglkskvzkgiwa@viti.kaiser.cx>
On Wed, Aug 02, 2023 at 08:38:49PM +0200, Martin Kaiser wrote:
> Stephen Boyd (sboyd@kernel.org) wrote:
>
> > You need to Cc linux-imx@nxp.com on imx clk patches. I think Abel has
> > some filter that looks for linux-clk@vger and linux-imx.
>
> > Also, please don't send series replies to previous rounds. It buries the
> > patches deep in my MUA and my scripts don't work well to apply patches
> > when they're sent like that.
>
> > I presume that Abel will pick the patches up? Or do you want to land
> > them through Arnd's tree? Either way feel free to add my acked-by
>
> > Acked-by: Stephen Boyd <sboyd@kernel.org>
>
> Thanks for responding, Stephen.
>
> Ok, understood. I'll resend with Cc linux-imx@nxp.com and without the
> reply to previous versions.
>
> Arnd, are you ok with taking these patches through your tree as
> suggested by Stephen?
I prefer to have Abel apply the patches through clk tree rather than
arm-soc tree, unless there is a good reason for them to go via the
latter.
Shawn
_______________________________________________
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:[~2023-08-06 3:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 8:03 [PATCH 0/3] ARM: imx25: print silicon revision, support 1.2 Martin Kaiser
2022-06-02 8:03 ` [PATCH 1/3] ARM: imx25: support silicon revision 1.2 Martin Kaiser
2022-06-19 3:40 ` Shawn Guo
2022-06-02 8:03 ` [PATCH 2/3] clk: imx25: print silicon revision during init Martin Kaiser
2022-06-02 8:03 ` [PATCH 3/3] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2022-06-23 7:51 ` [PATCH v2 0/2] ARM: imx25: print silicon revision at startup Martin Kaiser
2022-06-23 7:51 ` [PATCH v2 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2022-06-23 7:51 ` [PATCH v2 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2022-07-24 17:47 ` [PATCH v3 0/2] ARM: imx25: print silicon revision at startup Martin Kaiser
2022-07-24 17:47 ` [PATCH v3 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2022-07-25 10:53 ` Fabio Estevam
2022-07-24 17:47 ` [PATCH v3 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2022-07-25 10:54 ` Fabio Estevam
2022-08-15 19:07 ` [PATCH v4 0/2] ARM: imx25: print silicon revision at startup Martin Kaiser
2022-08-15 19:07 ` [PATCH v4 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2022-08-15 19:07 ` [PATCH v4 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2023-05-17 15:39 ` [PATCH v5 0/2] ARM: imx25: print silicon revision at startup Martin Kaiser
2023-05-17 15:39 ` [PATCH v5 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2023-05-17 15:39 ` [PATCH v5 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2023-05-17 18:21 ` [PATCH v5 0/2] ARM: imx25: print silicon revision at startup Arnd Bergmann
2023-07-30 16:39 ` [PATCH v6 " Martin Kaiser
2023-07-30 16:39 ` [PATCH v6 1/2] clk: imx25: print silicon revision during init Martin Kaiser
2023-07-30 16:39 ` [PATCH v6 2/2] clk: imx25: make __mx25_clocks_init return void Martin Kaiser
2023-08-01 19:13 ` [PATCH v6 0/2] ARM: imx25: print silicon revision at startup Stephen Boyd
2023-08-02 18:38 ` Martin Kaiser
2023-08-06 3:23 ` Shawn Guo [this message]
2023-08-07 14:38 ` Martin Kaiser
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=20230806032353.GX151430@dragon \
--to=shawnguo@kernel.org \
--cc=abelvesa@kernel.org \
--cc=arnd@arndb.de \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@kaiser.cx \
--cc=sboyd@kernel.org \
/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).