[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqLD=qzXiAptsR4X16_tYwSocFhrLJ=yh6caw1ke8YdESQ@mail.gmail.com>
Date: Fri, 28 Sep 2018 11:00:13 -0500
From: Rob Herring <robh@...nel.org>
To: Lee Jones <lee.jones@...aro.org>
Cc: Charles Keepax <ckeepax@...nsource.cirrus.com>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
patches@...nsource.cirrus.com
Subject: Re: [PATCH] mfd: arizona: Correct link for sound binding document
On Fri, Sep 28, 2018 at 12:46 AM Lee Jones <lee.jones@...aro.org> wrote:
>
> On Wed, 26 Sep 2018, Rob Herring wrote:
>
> > On Mon, Sep 17, 2018 at 04:33:22PM +0100, Charles Keepax wrote:
> > > Signed-off-by: Charles Keepax <ckeepax@...nsource.cirrus.com>
> > > ---
> > > Documentation/devicetree/bindings/mfd/arizona.txt | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Applied.
>
> Probably won't do any harm in this instance, but it's usually better
> for MFD binding changes to go through the MFD tree to avoid
> merge-conflicts.
It had been sitting there for a while, so I picked it up. Plus if we
have conflicts within a binding (other than tree wide clean ups I do),
that's not a good sign that the binding is changing.
Rob
Powered by blists - more mailing lists