[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOc5a3Mi1_oAOrA9t-2=0TVbs9Xr_HPBr_O+L7FgyAiRdf8sPg@mail.gmail.com>
Date: Fri, 12 Apr 2024 09:11:19 +0200
From: Lukas Bulwahn <lbulwahn@...hat.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>, Andi Shyti <andi.shyti@...nel.org>,
Lukas Bulwahn <lbulwahn@...hat.com>, Animesh Agarwal <animeshagarwal28@...il.com>,
linux-i2c@...r.kernel.org, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org, Lukas Bulwahn <lukas.bulwahn@...hat.com>
Subject: Re: [PATCH] MAINTAINERS: adjust file entry in ARM/LPC32XX SOC SUPPORT
On Fri, Apr 12, 2024 at 8:45 AM Wolfram Sang
<wsa+renesas@...g-engineering.com> wrote:
>
>
> > > -F: Documentation/devicetree/bindings/i2c/i2c-pnx.txt
> > > +F: Documentation/devicetree/bindings/i2c/nxp,pnx-i2c.yaml
> >
> > Reviewed-by: Andi Shyti <andi.shyti@...nel.org>
> >
> > I guess this should go through the arm folks?
>
> Could be argued, but I guess it is easier if you take it (because the
> conversion patch also went through your tree). Just 2 cents...
>
.. and I am creating my patches against some recent linux-next tag.
So, the commit could really only be in your tree and the arm folks
would not apply it because the referred commit is not in their tree
yet (until the next merge window closes and they reopen a new branch).
So, as Wolfram suggested: please take my patch in your tree on top of
the referred commit.
Lukas
Powered by blists - more mailing lists