From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Shawn Guo <shawnguo@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, yibin.gong@nxp.com,
Michael Turquette <mturquette@baylibre.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-imx@nxp.com, kernel@pengutronix.de,
"A.s. Dong" <aisheng.dong@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Russell King <linux@armlinux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Leonard Crestez <leonard.crestez@nxp.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v9 3/6] kernel/reboot.c: export pm_power_off_prepare
Date: Tue, 11 Sep 2018 06:36:35 +0200 [thread overview]
Message-ID: <134a7f76-6e0b-1a9f-26da-f01adaac44e6@pengutronix.de> (raw)
In-Reply-To: <20180911015320.GA25790@dragon>
[-- Attachment #1.1: Type: text/plain, Size: 1314 bytes --]
Hi Shawn,
On 11.09.2018 03:53, Shawn Guo wrote:
> On Mon, Sep 10, 2018 at 04:19:26PM +0100, Mark Brown wrote:
>> On Sun, Sep 09, 2018 at 10:00:23AM +0800, Shawn Guo wrote:
>>> On Thu, Sep 06, 2018 at 11:15:17AM +0100, Mark Brown wrote:
>>
>>>> I was expecting to get a pull request with the precursor patches in it -
>>>> the regulator driver seems to get a moderate amount of development so
>>>> there's a reasonable risk of conflicts.
>>
>>> What about you create a stable topic branch for regulator patches and I
>>> pull it into IMX tree?
>>
>> Sure, I can send a pull request back but the first two patches in the
>> series are ARM ones - are you OK with me just applying them and sending
>> them in the pull request or do you want to apply them first?
>
> I just took another look at the series. It seems that there is no
> build-time dependency between regulator and platform patches. So I
> think we can handle the series like:
>
> - You apply patch #3, #4 and #5 on regulator tree;
> - I apply the reset on IMX tree.
>
> There shouldn't be any build or run time regression on either tree, and
> the feature that the series adds will be available when both trees get
> merged together on -next or Linus tree.
>
> @Oleksij Is my understanding above correct?
Yes.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Shawn Guo <shawnguo@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Leonard Crestez <leonard.crestez@nxp.com>,
linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-imx@nxp.com, kernel@pengutronix.de,
Fabio Estevam <fabio.estevam@nxp.com>,
Russell King <linux@armlinux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
yibin.gong@nxp.com, "A.s. Dong" <aisheng.dong@nxp.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v9 3/6] kernel/reboot.c: export pm_power_off_prepare
Date: Tue, 11 Sep 2018 06:36:35 +0200 [thread overview]
Message-ID: <134a7f76-6e0b-1a9f-26da-f01adaac44e6@pengutronix.de> (raw)
In-Reply-To: <20180911015320.GA25790@dragon>
[-- Attachment #1.1.1: Type: text/plain, Size: 1314 bytes --]
Hi Shawn,
On 11.09.2018 03:53, Shawn Guo wrote:
> On Mon, Sep 10, 2018 at 04:19:26PM +0100, Mark Brown wrote:
>> On Sun, Sep 09, 2018 at 10:00:23AM +0800, Shawn Guo wrote:
>>> On Thu, Sep 06, 2018 at 11:15:17AM +0100, Mark Brown wrote:
>>
>>>> I was expecting to get a pull request with the precursor patches in it -
>>>> the regulator driver seems to get a moderate amount of development so
>>>> there's a reasonable risk of conflicts.
>>
>>> What about you create a stable topic branch for regulator patches and I
>>> pull it into IMX tree?
>>
>> Sure, I can send a pull request back but the first two patches in the
>> series are ARM ones - are you OK with me just applying them and sending
>> them in the pull request or do you want to apply them first?
>
> I just took another look at the series. It seems that there is no
> build-time dependency between regulator and platform patches. So I
> think we can handle the series like:
>
> - You apply patch #3, #4 and #5 on regulator tree;
> - I apply the reset on IMX tree.
>
> There shouldn't be any build or run time regression on either tree, and
> the feature that the series adds will be available when both trees get
> merged together on -next or Linus tree.
>
> @Oleksij Is my understanding above correct?
Yes.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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: o.rempel@pengutronix.de (Oleksij Rempel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 3/6] kernel/reboot.c: export pm_power_off_prepare
Date: Tue, 11 Sep 2018 06:36:35 +0200 [thread overview]
Message-ID: <134a7f76-6e0b-1a9f-26da-f01adaac44e6@pengutronix.de> (raw)
In-Reply-To: <20180911015320.GA25790@dragon>
Hi Shawn,
On 11.09.2018 03:53, Shawn Guo wrote:
> On Mon, Sep 10, 2018 at 04:19:26PM +0100, Mark Brown wrote:
>> On Sun, Sep 09, 2018 at 10:00:23AM +0800, Shawn Guo wrote:
>>> On Thu, Sep 06, 2018 at 11:15:17AM +0100, Mark Brown wrote:
>>
>>>> I was expecting to get a pull request with the precursor patches in it -
>>>> the regulator driver seems to get a moderate amount of development so
>>>> there's a reasonable risk of conflicts.
>>
>>> What about you create a stable topic branch for regulator patches and I
>>> pull it into IMX tree?
>>
>> Sure, I can send a pull request back but the first two patches in the
>> series are ARM ones - are you OK with me just applying them and sending
>> them in the pull request or do you want to apply them first?
>
> I just took another look at the series. It seems that there is no
> build-time dependency between regulator and platform patches. So I
> think we can handle the series like:
>
> - You apply patch #3, #4 and #5 on regulator tree;
> - I apply the reset on IMX tree.
>
> There shouldn't be any build or run time regression on either tree, and
> the feature that the series adds will be available when both trees get
> merged together on -next or Linus tree.
>
> @Oleksij Is my understanding above correct?
Yes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180911/72ac4272/attachment.sig>
next prev parent reply other threads:[~2018-09-11 4:37 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 10:34 [PATCH v9 0/6] provide power off support for iMX6 with external PMIC Oleksij Rempel
2018-08-02 10:34 ` Oleksij Rempel
2018-08-02 10:34 ` [PATCH v9 1/6] ARM: imx6q: provide documentation for new fsl,pmic-stby-poweroff property Oleksij Rempel
2018-08-02 10:34 ` [PATCH v9 1/6] ARM: imx6q: provide documentation for new fsl, pmic-stby-poweroff property Oleksij Rempel
2018-09-12 1:04 ` [PATCH v9 1/6] ARM: imx6q: provide documentation for new fsl,pmic-stby-poweroff property Shawn Guo
2018-09-12 1:04 ` Shawn Guo
2018-08-02 10:34 ` [PATCH v9 2/6] ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" is set Oleksij Rempel
2018-08-02 10:34 ` [PATCH v9 2/6] ARM: imx6: register pm_power_off handler if "fsl, pmic-stby-poweroff" " Oleksij Rempel
2018-09-12 1:10 ` [PATCH v9 2/6] ARM: imx6: register pm_power_off handler if "fsl,pmic-stby-poweroff" " Shawn Guo
2018-09-12 1:10 ` Shawn Guo
2018-08-02 10:34 ` [PATCH v9 3/6] kernel/reboot.c: export pm_power_off_prepare Oleksij Rempel
2018-08-02 10:34 ` Oleksij Rempel
2018-08-02 10:44 ` Mark Brown
2018-08-02 10:44 ` Mark Brown
2018-08-02 10:44 ` Mark Brown
2018-08-02 10:47 ` Oleksij Rempel
2018-08-02 10:47 ` Oleksij Rempel
2018-08-02 11:35 ` Mark Brown
2018-08-02 11:35 ` Mark Brown
2018-08-27 1:48 ` Shawn Guo
2018-08-27 1:48 ` Shawn Guo
2018-09-06 10:15 ` Mark Brown
2018-09-06 10:15 ` Mark Brown
2018-09-07 7:35 ` Oleksij Rempel
2018-09-07 7:35 ` Oleksij Rempel
2018-09-09 2:00 ` Shawn Guo
2018-09-09 2:00 ` Shawn Guo
2018-09-09 2:00 ` Shawn Guo
2018-09-10 15:19 ` Mark Brown
2018-09-10 15:19 ` Mark Brown
2018-09-11 1:53 ` Shawn Guo
2018-09-11 1:53 ` Shawn Guo
2018-09-11 4:36 ` Oleksij Rempel [this message]
2018-09-11 4:36 ` Oleksij Rempel
2018-09-11 4:36 ` Oleksij Rempel
2018-09-11 15:19 ` Mark Brown
2018-09-11 15:19 ` Mark Brown
2018-08-02 10:34 ` [PATCH v9 4/6] regulator: pfuze100: add fsl,pmic-stby-poweroff property Oleksij Rempel
2018-08-02 10:34 ` [PATCH v9 4/6] regulator: pfuze100: add fsl, pmic-stby-poweroff property Oleksij Rempel
2018-08-02 10:34 ` [PATCH v9 5/6] regulator: pfuze100-regulator: provide pm_power_off_prepare handler Oleksij Rempel
2018-08-02 10:34 ` Oleksij Rempel
2018-08-02 10:34 ` Oleksij Rempel
2018-08-02 10:34 ` [PATCH v9 6/6] ARM: dts: imx6: RIoTboard provide standby on power off option Oleksij Rempel
2018-08-02 10:34 ` Oleksij Rempel
2018-09-12 1:11 ` Shawn Guo
2018-09-12 1:11 ` Shawn Guo
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=134a7f76-6e0b-1a9f-26da-f01adaac44e6@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shawnguo@kernel.org \
--cc=yibin.gong@nxp.com \
/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.