From: Abel Vesa <abel.vesa@linaro.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Abel Vesa <abel.vesa@nxp.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Jacky Bai <ping.bai@nxp.com>
Subject: Re: [PATCH 3/7] clk: imx93: Correct the edma1's parent clock
Date: Thu, 16 Jun 2022 17:18:20 +0300 [thread overview]
Message-ID: <Yqs7rPynoWBi0XoY@ryzen> (raw)
In-Reply-To: <DU0PR04MB9417B711D79B0DE67D425E7B88AC9@DU0PR04MB9417.eurprd04.prod.outlook.com>
On 22-06-16 03:58:10, Peng Fan wrote:
> > Subject: Re: [PATCH 3/7] clk: imx93: Correct the edma1's parent clock
> >
> > Quoting Abel Vesa (2022-06-15 14:39:27)
> > > On 22-06-09 21:28:58, Peng Fan (OSS) wrote:
> > > > From: Jacky Bai <ping.bai@nxp.com>
> > > >
> > > > For EDMA1 in AONMIX, its parent clock should be from cm33_root, so
> > > > Correct it.
> > > >
> > > > Fixes: 24defbe194b65("clk: imx: add i.MX93 clk")
> > > > Reviewed-by: Peng Fan <peng.fan@nxp.com>
> > >
> > > The reviews done internally do no count in upstream.
> > > I think that's the rule. So drop the R-b tags from all patches.
> > > Keep only the S-o-b tags.
> >
> > Is it any different code from what is sent upstream here? If not any different
> > then I don't think anything is stopping the review tags from being kept.
>
> There is no difference, I directly cherry-pick downstream patch to upstream,
> with only a very minor subject change, dropping the JIRA ticket number.
>
Sounds good to me then. I'll apply it now. Thanks.
> Thanks,
> Peng.
_______________________________________________
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-06-16 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 13:28 [PATCH 0/7] clk: imx93: pll/imx93 fixes and update Peng Fan (OSS)
2022-06-09 13:28 ` [PATCH 1/7] clk: imx93: use adc_root as the parent clock of adc1 Peng Fan (OSS)
2022-06-15 21:31 ` Abel Vesa
2022-06-09 13:28 ` [PATCH 2/7] clk: imx93: correct nic_media parent Peng Fan (OSS)
2022-06-15 21:33 ` Abel Vesa
2022-06-09 13:28 ` [PATCH 3/7] clk: imx93: Correct the edma1's parent clock Peng Fan (OSS)
2022-06-15 21:39 ` Abel Vesa
2022-06-16 0:16 ` Stephen Boyd
2022-06-16 3:58 ` Peng Fan
2022-06-16 14:18 ` Abel Vesa [this message]
2022-06-09 13:28 ` [PATCH 4/7] clk: imx: clk-fracn-gppll: fix mfd value Peng Fan (OSS)
2022-06-09 13:29 ` [PATCH 5/7] clk: imx: clk-fracn-gppll: Return rate in rate table properly in ->recalc_rate() Peng Fan (OSS)
2022-06-09 13:29 ` [PATCH 6/7] clk: imx: clk-fracn-gppll: correct rdiv Peng Fan (OSS)
2022-06-09 13:29 ` [PATCH 7/7] clk: imx: clk-fracn-gppll: Add more freq config for video pll Peng Fan (OSS)
2022-06-16 16:01 ` [PATCH 0/7] clk: imx93: pll/imx93 fixes and update Abel Vesa
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=Yqs7rPynoWBi0XoY@ryzen \
--to=abel.vesa@linaro.org \
--cc=abel.vesa@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=ping.bai@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).