From: Chen-Yu Tsai <wens@csie.org>
To: Mark Brown <broonie@kernel.org>
Cc: Chen-Yu Tsai <wens@csie.org>, Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Carlo Caione <carlo@caione.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-sunxi <linux-sunxi@googlegroups.com>
Subject: Re: [PATCH v6 3/6] regulator: axp20x: prepare support for multiple AXP chip families
Date: Thu, 9 Apr 2015 20:36:44 -0700 [thread overview]
Message-ID: <CAGb2v64hsRV1S1E=9t1Gezx-HPT_mzVNc8p7hy_4jcoj5-1bsw@mail.gmail.com> (raw)
In-Reply-To: <20150409203634.GD6023@sirena.org.uk>
On Thu, Apr 9, 2015 at 1:36 PM, Mark Brown <broonie@kernel.org> wrote:
> On Thu, Apr 09, 2015 at 01:30:25PM -0700, Chen-Yu Tsai wrote:
>> On Thu, Apr 9, 2015 at 12:55 PM, Mark Brown <broonie@kernel.org> wrote:
>
>> > Someone would need to resend them to me as I've deleted them and it
>> > appears that this is a part of a series - are you sure there are no
>> > dependencies?
>
>> The 2 patches only touch drivers/regulator/axp20x-regulator.c.
>> Unless someone else is doing cleanup on them (AFAIK no one has),
>> there should be no problem.
>
> No header file dependencies?
The next patch (4/6) depends on mfd headers. That's why I'm asking
if the whole series, including the regulator patches, could go
through the mfd tree.
>> In any case, I will resend them after 4.1-rc1 if they aren't merged
>> by then.
>
> To be clear there is no chance they will be applied if they're not
> resent before the merge window.
Got it. I'll resend it with comments to clarify what I'm asking.
ChenYu
WARNING: multiple messages have this Message-ID (diff)
From: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Boris BREZILLON
<boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Carlo Caione <carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-sunxi <linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: [PATCH v6 3/6] regulator: axp20x: prepare support for multiple AXP chip families
Date: Thu, 9 Apr 2015 20:36:44 -0700 [thread overview]
Message-ID: <CAGb2v64hsRV1S1E=9t1Gezx-HPT_mzVNc8p7hy_4jcoj5-1bsw@mail.gmail.com> (raw)
In-Reply-To: <20150409203634.GD6023-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Thu, Apr 9, 2015 at 1:36 PM, Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> On Thu, Apr 09, 2015 at 01:30:25PM -0700, Chen-Yu Tsai wrote:
>> On Thu, Apr 9, 2015 at 12:55 PM, Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>
>> > Someone would need to resend them to me as I've deleted them and it
>> > appears that this is a part of a series - are you sure there are no
>> > dependencies?
>
>> The 2 patches only touch drivers/regulator/axp20x-regulator.c.
>> Unless someone else is doing cleanup on them (AFAIK no one has),
>> there should be no problem.
>
> No header file dependencies?
The next patch (4/6) depends on mfd headers. That's why I'm asking
if the whole series, including the regulator patches, could go
through the mfd tree.
>> In any case, I will resend them after 4.1-rc1 if they aren't merged
>> by then.
>
> To be clear there is no chance they will be applied if they're not
> resent before the merge window.
Got it. I'll resend it with comments to clarify what I'm asking.
ChenYu
WARNING: multiple messages have this Message-ID (diff)
From: wens@csie.org (Chen-Yu Tsai)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/6] regulator: axp20x: prepare support for multiple AXP chip families
Date: Thu, 9 Apr 2015 20:36:44 -0700 [thread overview]
Message-ID: <CAGb2v64hsRV1S1E=9t1Gezx-HPT_mzVNc8p7hy_4jcoj5-1bsw@mail.gmail.com> (raw)
In-Reply-To: <20150409203634.GD6023@sirena.org.uk>
On Thu, Apr 9, 2015 at 1:36 PM, Mark Brown <broonie@kernel.org> wrote:
> On Thu, Apr 09, 2015 at 01:30:25PM -0700, Chen-Yu Tsai wrote:
>> On Thu, Apr 9, 2015 at 12:55 PM, Mark Brown <broonie@kernel.org> wrote:
>
>> > Someone would need to resend them to me as I've deleted them and it
>> > appears that this is a part of a series - are you sure there are no
>> > dependencies?
>
>> The 2 patches only touch drivers/regulator/axp20x-regulator.c.
>> Unless someone else is doing cleanup on them (AFAIK no one has),
>> there should be no problem.
>
> No header file dependencies?
The next patch (4/6) depends on mfd headers. That's why I'm asking
if the whole series, including the regulator patches, could go
through the mfd tree.
>> In any case, I will resend them after 4.1-rc1 if they aren't merged
>> by then.
>
> To be clear there is no chance they will be applied if they're not
> resent before the merge window.
Got it. I'll resend it with comments to clarify what I'm asking.
ChenYu
next prev parent reply other threads:[~2015-04-10 3:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 6:03 [PATCH v6 0/6] mfd: axp20x: add AXP221 PMIC support Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` [PATCH v6 1/6] mfd: axp20x: add AXP22x " Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 7:12 ` Lee Jones
2015-04-01 7:12 ` Lee Jones
2015-04-01 7:12 ` Lee Jones
2015-04-01 7:17 ` Chen-Yu Tsai
2015-04-01 7:17 ` Chen-Yu Tsai
2015-04-01 6:03 ` [PATCH v6 2/6] mfd: axp20x: update DT bindings with AXP22x compatibles Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` [PATCH v6 3/6] regulator: axp20x: prepare support for multiple AXP chip families Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-09 17:23 ` Chen-Yu Tsai
2015-04-09 17:23 ` Chen-Yu Tsai
2015-04-09 17:23 ` Chen-Yu Tsai
2015-04-09 19:55 ` Mark Brown
2015-04-09 19:55 ` Mark Brown
2015-04-09 19:55 ` Mark Brown
2015-04-09 20:30 ` Chen-Yu Tsai
2015-04-09 20:30 ` Chen-Yu Tsai
2015-04-09 20:30 ` Chen-Yu Tsai
2015-04-09 20:36 ` Mark Brown
2015-04-09 20:36 ` Mark Brown
2015-04-09 20:36 ` Mark Brown
2015-04-10 3:36 ` Chen-Yu Tsai [this message]
2015-04-10 3:36 ` Chen-Yu Tsai
2015-04-10 3:36 ` Chen-Yu Tsai
2015-04-01 6:03 ` [PATCH v6 4/6] regulator: axp20x: add support for AXP22X regulators Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` [PATCH v6 5/6] mfd: axp20x: Add AXP22x regulator information to DT bindings Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 7:10 ` Lee Jones
2015-04-01 7:10 ` Lee Jones
2015-04-01 7:10 ` Lee Jones
2015-04-01 6:03 ` [PATCH v6 6/6] mfd: axp20x: Enable AXP22X regulators Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
2015-04-01 6:03 ` Chen-Yu Tsai
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='CAGb2v64hsRV1S1E=9t1Gezx-HPT_mzVNc8p7hy_4jcoj5-1bsw@mail.gmail.com' \
--to=wens@csie.org \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.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.