From: "Kim, Milo" <milo.kim@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: lee.jones@linaro.org, robh+dt@kernel.org,
j.anaszewski@samsung.com, devicetree@vger.kernel.org,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 9/9] regulator: add LM363X driver
Date: Fri, 15 Jan 2016 08:41:47 +0900 [thread overview]
Message-ID: <5698323B.4030401@ti.com> (raw)
In-Reply-To: <20160114102736.GP6588@sirena.org.uk>
On 1/14/2016 7:27 PM, Mark Brown wrote:
> On Thu, Jan 14, 2016 at 04:56:03PM +0900, Milo Kim wrote:
>
>> So, I'd like to know which is better for you.
>> a) Create a patch based on linux-next tree (the above patch)
>> Or
>> b) Re-generate a patch based on linux-mfd tree
>
> At this point the easiest thing might be to wait for v4.5-rc1 then send
> a patch for that after everything gets merged.
OK, thanks!
Best regards,
Milo
WARNING: multiple messages have this Message-ID (diff)
From: "Kim, Milo" <milo.kim@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lee.jones@linaro.org>, <robh+dt@kernel.org>,
<j.anaszewski@samsung.com>, <devicetree@vger.kernel.org>,
<linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 9/9] regulator: add LM363X driver
Date: Fri, 15 Jan 2016 08:41:47 +0900 [thread overview]
Message-ID: <5698323B.4030401@ti.com> (raw)
In-Reply-To: <20160114102736.GP6588@sirena.org.uk>
On 1/14/2016 7:27 PM, Mark Brown wrote:
> On Thu, Jan 14, 2016 at 04:56:03PM +0900, Milo Kim wrote:
>
>> So, I'd like to know which is better for you.
>> a) Create a patch based on linux-next tree (the above patch)
>> Or
>> b) Re-generate a patch based on linux-mfd tree
>
> At this point the easiest thing might be to wait for v4.5-rc1 then send
> a patch for that after everything gets merged.
OK, thanks!
Best regards,
Milo
next prev parent reply other threads:[~2016-01-14 23:41 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 6:56 [PATCH v2 0/9] Support TI LMU devices Milo Kim
2015-11-26 6:56 ` Milo Kim
2015-11-26 6:56 ` [PATCH v2 1/9] Documentation: dt-bindings: mfd: add TI LMU device binding information Milo Kim
2015-11-26 6:56 ` Milo Kim
2015-11-27 20:55 ` Rob Herring
2016-01-11 9:46 ` Lee Jones
2015-11-26 6:56 ` [PATCH v2 2/9] Documentation: dt-bindings: leds: backlight: add TI LMU backlight " Milo Kim
2015-11-26 6:56 ` Milo Kim
2016-01-11 9:53 ` Lee Jones
2015-11-26 6:56 ` [PATCH v2 3/9] Documentation: dt-bindings: leds: add LM3633 LED " Milo Kim
2015-11-26 6:56 ` Milo Kim
2015-11-27 11:19 ` Jacek Anaszewski
2015-11-30 8:19 ` Kim, Milo
2015-11-30 8:19 ` Kim, Milo
2015-11-30 12:26 ` Jacek Anaszewski
[not found] ` <565C408B.9070703-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-12-07 8:46 ` Kim, Milo
2015-12-07 8:46 ` Kim, Milo
2015-12-07 10:50 ` Jacek Anaszewski
2015-11-26 6:57 ` [PATCH v2 4/9] Documentation: dt-bindings: regulator: add LM363x regulator " Milo Kim
2015-11-26 6:57 ` Milo Kim
2015-11-27 12:37 ` Mark Brown
2015-11-27 20:44 ` Rob Herring
2015-11-27 22:07 ` Mark Brown
2015-11-27 12:55 ` Applied "regulator: lm363x: add LM363x regulator binding information" to the regulator tree Mark Brown
2015-11-27 20:57 ` [PATCH v2 4/9] Documentation: dt-bindings: regulator: add LM363x regulator binding information Rob Herring
2015-11-26 6:57 ` [PATCH v2 5/9] mfd: add TI LMU driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2016-01-11 10:17 ` Lee Jones
2015-11-26 6:57 ` [PATCH v2 6/9] mfd: add TI LMU hardware fault monitoring driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2016-01-11 10:21 ` Lee Jones
2016-01-12 3:36 ` Milo Kim
2016-01-12 3:36 ` Milo Kim
2016-01-12 7:37 ` Lee Jones
2015-11-26 6:57 ` [PATCH v2 7/9] backlight: add TI LMU backlight driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2016-01-11 9:57 ` Lee Jones
2016-01-11 23:32 ` Milo Kim
2016-01-11 23:32 ` Milo Kim
2015-11-26 6:57 ` [PATCH v2 8/9] leds: add LM3633 driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2015-11-27 11:19 ` Jacek Anaszewski
[not found] ` <56583C37.1050307-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-11-28 8:28 ` Jacek Anaszewski
2015-11-28 8:28 ` Jacek Anaszewski
2015-11-30 8:48 ` Kim, Milo
2015-11-30 8:48 ` Kim, Milo
2015-11-30 12:26 ` Jacek Anaszewski
2015-11-26 6:57 ` [PATCH v2 9/9] regulator: add LM363X driver Milo Kim
2015-11-26 6:57 ` Milo Kim
2015-11-27 12:55 ` Applied "regulator: add LM363X driver" to the regulator tree Mark Brown
2016-01-14 7:56 ` [PATCH v2 9/9] regulator: add LM363X driver Milo Kim
2016-01-14 7:56 ` Milo Kim
[not found] ` <56975493.7050900-l0cyMroinI0@public.gmane.org>
2016-01-14 10:27 ` Mark Brown
2016-01-14 10:27 ` Mark Brown
2016-01-14 23:41 ` Kim, Milo [this message]
2016-01-14 23:41 ` Kim, Milo
2016-01-06 7:20 ` [PATCH v2 0/9] Support TI LMU devices Milo Kim
2016-01-06 7:20 ` Milo Kim
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=5698323B.4030401@ti.com \
--to=milo.kim@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh+dt@kernel.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 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.