All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Jun Li <jun.li@nxp.com>
Cc: Marco Felsch <m.felsch@pengutronix.de>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"marex@denx.de" <marex@denx.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Peng Fan <peng.fan@nxp.com>,
	"Markus.Niebel@ew.tq-group.com" <Markus.Niebel@ew.tq-group.com>,
	"laurent.pinchart@ideasonboard.com"
	<laurent.pinchart@ideasonboard.com>,
	"paul.elder@ideasonboard.com" <paul.elder@ideasonboard.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"aford173@gmail.com" <aford173@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"l.stach@pengutronix.de" <l.stach@pengutronix.de>
Subject: Re: [PATCH] arm64: dts: imx8mp: correct usb clocks
Date: Tue, 6 Sep 2022 18:18:37 +0800	[thread overview]
Message-ID: <20220906101837.GP1728671@dragon> (raw)
In-Reply-To: <PA4PR04MB9640FA621C9E03C167EFA607897E9@PA4PR04MB9640.eurprd04.prod.outlook.com>

On Tue, Sep 06, 2022 at 09:49:28AM +0000, Jun Li wrote:
> Hi Shawn,
> 
> > > > > Hi Li,
> > > > >
> > > > > On 22-08-24, Li Jun wrote:
> > > > > > After commit cf7f3f4fa9e5 ("clk: imx8mp: fix usb_root_clk
> > > > > > parent"), usb_root_clk is no longer for suspend clock so update
> > > > > > dts accordingly to use right bus clock and suspend clock.
> > > > >
> > > > > Please don't send two seperate patchsets for this topic, since
> > > > > they can be applied delayed. So your v2 should contain the patches
> > > > > from [1]
> > > > as well.
> > > >
> > > > Understood, I will put all in one patch set in v2.
> > >
> > > Since the clock part patches[1] already were accepted, I think this
> > > corresponding dts fix patch should be okay as it is.
> > 
> > Should I apply the DTS patch for v6.0-rc or v6.1?  My understanding is that
> > it needs to appear in the same release as clock patch[1], right?
> 
> Yes, it needs to appear in the same release as clock patch[1].

So could you find out which release the clock patch is targeting?

Shawn

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Jun Li <jun.li@nxp.com>
Cc: Marco Felsch <m.felsch@pengutronix.de>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"marex@denx.de" <marex@denx.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Peng Fan <peng.fan@nxp.com>,
	"Markus.Niebel@ew.tq-group.com" <Markus.Niebel@ew.tq-group.com>,
	"laurent.pinchart@ideasonboard.com" 
	<laurent.pinchart@ideasonboard.com>,
	"paul.elder@ideasonboard.com" <paul.elder@ideasonboard.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"aford173@gmail.com" <aford173@gmail.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"l.stach@pengutronix.de" <l.stach@pengutronix.de>
Subject: Re: [PATCH] arm64: dts: imx8mp: correct usb clocks
Date: Tue, 6 Sep 2022 18:18:37 +0800	[thread overview]
Message-ID: <20220906101837.GP1728671@dragon> (raw)
In-Reply-To: <PA4PR04MB9640FA621C9E03C167EFA607897E9@PA4PR04MB9640.eurprd04.prod.outlook.com>

On Tue, Sep 06, 2022 at 09:49:28AM +0000, Jun Li wrote:
> Hi Shawn,
> 
> > > > > Hi Li,
> > > > >
> > > > > On 22-08-24, Li Jun wrote:
> > > > > > After commit cf7f3f4fa9e5 ("clk: imx8mp: fix usb_root_clk
> > > > > > parent"), usb_root_clk is no longer for suspend clock so update
> > > > > > dts accordingly to use right bus clock and suspend clock.
> > > > >
> > > > > Please don't send two seperate patchsets for this topic, since
> > > > > they can be applied delayed. So your v2 should contain the patches
> > > > > from [1]
> > > > as well.
> > > >
> > > > Understood, I will put all in one patch set in v2.
> > >
> > > Since the clock part patches[1] already were accepted, I think this
> > > corresponding dts fix patch should be okay as it is.
> > 
> > Should I apply the DTS patch for v6.0-rc or v6.1?  My understanding is that
> > it needs to appear in the same release as clock patch[1], right?
> 
> Yes, it needs to appear in the same release as clock patch[1].

So could you find out which release the clock patch is targeting?

Shawn

  reply	other threads:[~2022-09-06 10:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  8:10 [PATCH] arm64: dts: imx8mp: correct usb clocks Li Jun
2022-08-24  8:10 ` Li Jun
2022-08-24  8:56 ` Lucas Stach
2022-08-24  8:56   ` Lucas Stach
2022-08-24 10:21   ` Jun Li
2022-08-24 10:21     ` Jun Li
2022-08-24  9:10 ` Marco Felsch
2022-08-24  9:10   ` Marco Felsch
2022-08-24 10:23   ` Jun Li
2022-08-24 10:23     ` Jun Li
2022-09-06  7:19     ` Jun Li
2022-09-06  7:19       ` Jun Li
2022-09-06  9:43       ` Shawn Guo
2022-09-06  9:43         ` Shawn Guo
2022-09-06  9:49         ` Jun Li
2022-09-06  9:49           ` Jun Li
2022-09-06 10:18           ` Shawn Guo [this message]
2022-09-06 10:18             ` Shawn Guo
2022-09-06 11:30             ` Jun Li
2022-09-06 11:30               ` Jun Li
2022-09-07 10:24               ` Abel Vesa
2022-09-07 10:24                 ` 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=20220906101837.GP1728671@dragon \
    --to=shawnguo@kernel.org \
    --cc=Markus.Niebel@ew.tq-group.com \
    --cc=aford173@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=jun.li@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=l.stach@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=m.felsch@pengutronix.de \
    --cc=marex@denx.de \
    --cc=paul.elder@ideasonboard.com \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.