All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	kernel@pengutronix.de, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Leonard Crestez <leonard.crestez@nxp.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Russell King <linux@armlinux.org.uk>,
	linux-imx@nxp.com, yibin.gong@nxp.com,
	"A.s. Dong" <aisheng.dong@nxp.com>
Subject: Re: [PATCH v9 3/6] kernel/reboot.c: export pm_power_off_prepare
Date: Mon, 10 Sep 2018 16:19:26 +0100	[thread overview]
Message-ID: <20180910151926.GA10889@sirena.org.uk> (raw)
In-Reply-To: <20180909020021.GA18838@dragon>

[-- Attachment #1: Type: text/plain, Size: 621 bytes --]

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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 3/6] kernel/reboot.c: export pm_power_off_prepare
Date: Mon, 10 Sep 2018 16:19:26 +0100	[thread overview]
Message-ID: <20180910151926.GA10889@sirena.org.uk> (raw)
In-Reply-To: <20180909020021.GA18838@dragon>

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?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180910/a549cbdc/attachment.sig>

  reply	other threads:[~2018-09-10 15:19 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 [this message]
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
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=20180910151926.GA10889@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=akpm@linux-foundation.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=o.rempel@pengutronix.de \
    --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.