From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH v2 03/11] dt-bindings: add device tree binding for X-Powers AXP803 PMIC
Date: Wed, 12 Apr 2017 09:06:02 +0100 [thread overview]
Message-ID: <20170412080602.f7cjeeht5r45cnvh@dell> (raw)
In-Reply-To: <20170411180844.9176B125521@relay.mailchannels.net>
On Wed, 12 Apr 2017, Icenowy Zheng wrote:
>
> 2017?4?12? ??12:29? Lee Jones <lee.jones@linaro.org>???
> >
> > On Tue, 11 Apr 2017, Chen-Yu Tsai wrote:
> >
> > > Hi,
> > >
> > > On Tue, Apr 11, 2017 at 11:00 PM, Icenowy Zheng <icenowy@aosc.io> wrote:
> > > >
> > > >
> > > > On Tue, 11 Apr 2017, Lee Jones wrote:
> > > >
> > > >> On Sat, 08 Apr 2017, Icenowy Zheng wrote:
> > > >>
> > > >>> AXP803 is a PMIC produced by Shenzhen X-Powers, with either I2C or RSB
> > > >>> bus.
> > > >>>
> > > >>> Add a compatible for it.
> > > >>>
> > > >>> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> > > >>> Acked-by: Chen-Yu Tsai <wens@csie.org>
> > > >>> ---
> > > >>> Changes in v2:
> > > >>> - Place AXP803 before AXP806/809.
> > > >>> - Added Chen-Yu's ACK.
> > > >>>
> > > >>>? Documentation/devicetree/bindings/mfd/axp20x.txt | 5 +++--
> > > >>>? 1 file changed, 3 insertions(+), 2 deletions(-)
> > > >>
> > > >>
> > > >> For my own reference:
> > > >>? Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
> > > >
> > > >
> > > > Excuse me... Who will apply this patch?
> >
> > Excuse you?? Are you trying to be polite, or rude?
> >
> > I'm guessing due to the lagging '...', that it's the latter?
>
> Oh sorry, I mean the former...
Okay, no problem then.
> > > > I think this patch should be applied by you as it's in bindings/mfd
> > > > directory, however, if I'm wrong, please point out ;-)
> > >
> > > We need the DT maintainers to ack it first. :)
> >
> > We don't really need the DT Maintainers to get involved here.
> >
> > What I do need is either clear direction as to how this
> > patch-set should be applied, or an indication of which patches are
> > dependant on others and which are orthogonal and can be applied
> > independently.
>
> This patch is independent, although the regulator binding patch
> depends on it.
>
> The real driver patches will need the binding patches to be merged
> first.
Right, so Acking and not applying wasn't such a strange practice
after all then. =;-)
> And the dt patches depend on also the binding patches.
The issue I have now is; because your email client replies as a new
mail i.e. non-threaded, now I have no reference to the patch-set.
Since time is a valuable resource, I will not be dredging though my
inbox looking for all your replies.
Please fix your client before replying to another mail.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next parent reply other threads:[~2017-04-12 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170411180844.9176B125521@relay.mailchannels.net>
2017-04-12 8:06 ` Lee Jones [this message]
2017-04-07 18:34 [PATCH v2 00/11] AXP803 PMIC support for Pine64 Icenowy Zheng
2017-04-07 18:34 ` [PATCH v2 03/11] dt-bindings: add device tree binding for X-Powers AXP803 PMIC Icenowy Zheng
2017-04-11 14:04 ` Lee Jones
2017-04-11 15:00 ` Icenowy Zheng
2017-04-11 15:02 ` [linux-sunxi] " Chen-Yu Tsai
2017-04-11 16:29 ` Lee Jones
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=20170412080602.f7cjeeht5r45cnvh@dell \
--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