devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@dowhile0.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it
Date: Tue, 23 May 2017 10:46:17 +0200	[thread overview]
Message-ID: <CABxcv=n+BfADaoc0dG7hBBPZS2F6TtxgjhwBv8f=GVYSdjovGg@mail.gmail.com> (raw)
In-Reply-To: <CABxcv=nXhyuRwwhzv0H8mK98wUmAPDNPErkV92o9nRFZV2dEsw@mail.gmail.com>

Hello Lee,

On Fri, May 5, 2017 at 12:40 PM, Javier Martinez Canillas
<javier@dowhile0.org> wrote:
> Hello,
>
> On Thu, May 4, 2017 at 1:50 PM, Lee Jones <lee.jones@linaro.org> wrote:
>> On Thu, 04 May 2017, Wolfram Sang wrote:
>>> thanks for the series.
>>>
>>> > Most patches can be applied independently, with the exception of patches
>>> > 2 to 4 that should be applied in the same tree to keep bisect-ability. I
>>> > suggest these to go through the MFD subsystem tree.
>>>
>>> From my POV, patches 2-5 should be applied to the same tree. Since all
>
> Yes, I didn't mention 5 because is just a documentation change. But it
> would be better if is merged together with 2-4 indeed.
>
>>> I2C related patches have my tag, I assume they will be picked up by MFD.
>>> Lee, let me know if you prefer differently.
>>
>> I can pick them up, no problem.  Can the ARM patches be taking
>> independently?  I'm guessing they can since they are separate from one
>> another.
>>
>
> That's corect. The only platform changes that can't be picked
> independently from MFD are the ones in patch 2, but tha's why I added
> in the same patch. The OMAP folks (Tony and Aaro) already acked so you
> can pick it.
>

Is there anything else I need to do for you to pick this series?

Best regards,
Javier

  reply	other threads:[~2017-05-23  8:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04  5:20 [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it Javier Martinez Canillas
2017-05-04  5:21 ` [PATCH v6 2/8] mfd: retu: Drop -mfd suffix from I2C device ID name Javier Martinez Canillas
     [not found] ` <20170504052107.18995-1-javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org>
2017-05-04  5:21   ` [PATCH v6 1/8] dt-bindings: mfd: Add retu/tahvo ASIC chips bindings Javier Martinez Canillas
2017-05-04  5:21   ` [PATCH v6 3/8] mfd: retu: Add OF device ID table Javier Martinez Canillas
2017-05-04  5:21   ` [PATCH v6 4/8] ARM: dts: n8x0: Add vendor prefix to retu node Javier Martinez Canillas
2017-05-04  5:21   ` [PATCH v6 5/8] i2c: i2c-cbus-gpio: Add vendor prefix to retu node in example Javier Martinez Canillas
2017-05-04  5:21   ` [PATCH v6 6/8] dt-bindings: mfd: Add TI tps6105x chip bindings Javier Martinez Canillas
2017-05-04  5:21   ` [PATCH v6 8/8] ARM: ux500: Add vendor prefix to tps61052 node Javier Martinez Canillas
2017-05-23 15:41     ` Lee Jones
     [not found]     ` <20170504052107.18995-9-javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org>
2017-05-24  7:45       ` Javier Martinez Canillas
2017-05-29  9:36     ` Linus Walleij
2017-06-06  9:18       ` Javier Martinez Canillas
2017-05-04  8:09   ` [PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it Wolfram Sang
2017-05-04 11:50     ` Lee Jones
2017-05-05 10:40       ` Javier Martinez Canillas
2017-05-23  8:46         ` Javier Martinez Canillas [this message]
2017-05-04  5:21 ` [PATCH v6 7/8] mfd: tps6105x: Add OF device ID table Javier Martinez Canillas

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='CABxcv=n+BfADaoc0dG7hBBPZS2F6TtxgjhwBv8f=GVYSdjovGg@mail.gmail.com' \
    --to=javier@dowhile0.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.com \
    --cc=wsa@the-dreams.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 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).