public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH v6 0/7] mfd: AXP20x: Add support for AXP202 and AXP209
Date: Fri, 23 May 2014 11:12:36 +0100	[thread overview]
Message-ID: <20140523101236.GS19747@lee--X1> (raw)
In-Reply-To: <20140522195523.GB7708@core.coreip.homeip.net>

> > >> >> This set of patches introduces the core driver and support for two different
> > >> >> subsystems:
> > >> >>       - Regulators
> > >> >
> > >> >>  .../ABI/testing/sysfs-driver-input-axp-pek         |  11 +
> > >> >>  Documentation/devicetree/bindings/mfd/axp20x.txt   |  93 +++++++
> > >> >>  .../devicetree/bindings/vendor-prefixes.txt        |   1 +
> > >> >>  arch/arm/configs/multi_v7_defconfig                |   3 +
> > >> >>  arch/arm/configs/sunxi_defconfig                   |   4 +
> > >> >>  drivers/input/misc/Kconfig                         |  11 +
> > >> >>  drivers/input/misc/Makefile                        |   1 +
> > >> >>  drivers/input/misc/axp20x-pek.c                    | 281 +++++++++++++++++++++
> > >> >>  drivers/mfd/Kconfig                                |  12 +
> > >> >>  drivers/mfd/Makefile                               |   1 +
> > >> >>  drivers/mfd/axp20x.c                               | 258 +++++++++++++++++++
> > >> >>  include/linux/mfd/axp20x.h                         | 180 +++++++++++++
> > >> >>  12 files changed, 856 insertions(+)
> > >> >
> > >> > The regulator changes don't appear to be showing up in the diffstat or
> > >> > obviously in the series?
> > >>
> > >> Right. Cut-and-paste error.
> > >> You have already applied the regulator patches so I didn't include
> > >> them here (in theory I posted this series to be picked up by Lee).
> > >
> > > That's fine.  Just tell me which patches need to stay together and
> > > which are able to be applied through their respective subsystem trees
> > > separately.  Then, once I have all the Acks I can apply no problem.
> > 
> > Hi Lee,
> > I'd say #1 for the MFD tree, #4 for the input subsystem, #2 #3 and #5
> > are documentations, #6 and #7 defconfigs add-on.
> 
> I am fine with the input piece going through MFD tree, no need to split
> it from the rest.

Do you want a pull-request i.e. will this cause conflicts when Linus
merges it with your tree, or is it okay for me to just apply it?

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2014-05-23 10:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 19:47 [PATCH v6 0/7] mfd: AXP20x: Add support for AXP202 and AXP209 Carlo Caione
2014-05-19 19:47 ` [PATCH v6 1/7] mfd: AXP20x: Add mfd driver for AXP20x PMIC Carlo Caione
2014-05-19 19:47 ` [PATCH v6 2/7] dt-bindings: add vendor-prefix for X-Powers Carlo Caione
2014-05-19 19:47 ` [PATCH v6 3/7] mfd: AXP20x: Add bindings documentation Carlo Caione
2014-06-17  7:24   ` Boris BREZILLON
2014-06-18  9:06     ` Lee Jones
2014-06-21  8:52       ` [linux-sunxi] " Carlo Caione
2014-05-19 19:47 ` [PATCH v6 4/7] input: misc: Add driver for AXP20x Power Enable Key Carlo Caione
2014-05-19 19:47 ` [PATCH v6 5/7] input: misc: Add ABI docs for AXP20x PEK Carlo Caione
2014-05-19 19:47 ` [PATCH v6 6/7] ARM: sunxi: Add AXP20x support in defconfig Carlo Caione
2014-05-19 19:47 ` [PATCH v6 7/7] ARM: sunxi: Add AXP20x support multi_v7_defconfig Carlo Caione
2014-05-20 22:23 ` [PATCH v6 0/7] mfd: AXP20x: Add support for AXP202 and AXP209 Mark Brown
2014-05-21  7:24   ` Carlo Caione
2014-05-21  9:14     ` Lee Jones
2014-05-22 19:15       ` [linux-sunxi] " Carlo Caione
2014-05-22 19:55         ` Dmitry Torokhov
2014-05-23 10:12           ` Lee Jones [this message]

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=20140523101236.GS19747@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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