[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8834220.fknQf5gIhd@avalon>
Date: Mon, 10 Sep 2018 12:46:00 +0300
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Phil Edworthy <phil.edworthy@...esas.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
jacopo <jacopo@...ndi.org>, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Simon Horman <horms@...ge.net.au>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] Renesas R9A06G032 PINCTRL Driver
Hello,
On Monday, 10 September 2018 10:48:58 EEST Linus Walleij wrote:
> On Wed, Sep 5, 2018 at 11:59 AM Phil Edworthy wrote:
> > On 05 September 2018 10:37, Geert Uytterhoeven wrote:
> > > Have the VxWorks DT bindings been submitted for review to the devicetree
> > > mailing list?
> >
> > I'm not involved with the VxWorks port, but I am pretty sure that they
> > have not been submitted for review.
>
> We have had other cases where deployments on other OSes have been
> establishing bindings (even not very pretty ones).
I hardly see that as a good reason to accept the bindings blindly. If they
haven't been submitted for review, it's their problem, not ours. Even worse in
my opinion is the fact that those bindings are used by the "out-of-tree Linux
port". We've hammered the "upstream first" message for years if not decades,
if the industry still can't get it, I don't see why we should be the ones
suffering.
No ack from me for these new bindings, sorry.
> Examples include typically the Power MacIntosh and the original SPARC
> bindings.
--
Regards,
Laurent Pinchart
Powered by blists - more mailing lists