[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180525142322.GA25453@linaro.org>
Date: Fri, 25 May 2018 19:53:22 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Andreas Färber <afaerber@...e.de>,
Rob Herring <robh+dt@...nel.org>, liuwei@...ions-semi.com,
96boards@...obotics.com,
OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
<devicetree@...r.kernel.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Daniel Thompson <daniel.thompson@...aro.org>,
Amit Kucheria <amit.kucheria@...aro.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
GPIO SUBSYSTEM <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
hzhang@...obotics.com, bdong@...obotics.com,
Mani Sadhasivam <manivannanece23@...il.com>,
"Thomas C. Liau" <thomas.liau@...ions-semi.com>,
Jeff Chen <jeff.chen@...ions-semi.com>
Subject: Re: [PATCH v2 5/5] MAINTAINERS: Add Actions Semi S900 pinctrl entries
On Fri, May 25, 2018 at 02:12:06PM +0200, Linus Walleij wrote:
> On Fri, May 25, 2018 at 7:01 AM, Manivannan Sadhasivam
> <manivannan.sadhasivam@...aro.org> wrote:
>
> > FYI, I have ordered S700 based Cubieboard and will work on adding support for
> > that first. I still don't have access to S500 board yet since it is not
> > available on my region. Will find a way to get this asap.
>
> Awesome, then we can count on some actions action here.
>
Oops... Small correction here, I have ordered S500 based board.
> >> Also I had been investing efforts in explaining the upstreaming process
> >> to Actions, last in November. I see Thomas Liau and Jeff Chen missing in
> >> CC and I have not seen any Reviewed-by or Acked-by from anyone at
> >> Actions on this and the preceding series. There are more chips than the
> >> one on Linaro's 96board, so I would prefer to assure that the design
> >> works for all. Thus I am very critical of you applying the patches
> >> without waiting for review by Actions.
> >
> > I don't think Actions would be interested in any upstreaming efforts. It
> > is our (comunity) responsibility to add support for that in order to
> > have our boards running mainline kernel and that's what we both have been
> > doing. Moreover I only saw once David Liau responded to your patchset and
> > there isn't much further. So how can you expect the subsystem maintainer's
> > to hold the patch series waiting for a so far silent SoC manufacturer's
> > response?
>
> They are certainly informed now! :D
>
> Actions semi folks, please familiarize yourself with the following:
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/tree/Documentation/devicetree/bindings/pinctrl/actions,s900-pinctrl.txt?h=devel
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/tree/drivers/pinctrl/actions?h=devel
>
> If you have any concerns with this, now is a good time to share them.
>
> > I
> > did ask you to add me as Co-Maintainer but you didn't responded to that.
> > I know that I can't send any pull requests to Arnd, but we should sort
> > it out IMO. Also, if you are completely swamped, then I take take up the
> > maintainership role now inorder to keep the things moving. TBH I don't
> > want my patches to be floating for months without any reason.
>
> Doing some comainatinership can very well include doing pull
> requests as long as you agree on who does what.
>
> I think it may be a bit late for the next merge window right now,
> but if you simply queue up stuff in some git tree and ask
> Srothwell to include it in linux-next then Andreas can very well
> pull it to his tree from there and then to ARM SoC or you can
> queue patches as well.
>
Cool. Will queue up all approved dts patches in a git tree and share it with
andreas.
Thanks,
Mani
> Yours,
> Linus Walleij
Powered by blists - more mailing lists