[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfiaWFricM4Or771P0LJVoFoEmQtoJo1hySo=BRS-59DQ@mail.gmail.com>
Date: Fri, 8 Mar 2024 12:34:24 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Arnd Bergmann <arnd@...nel.org>
Cc: Gregory Clement <gregory.clement@...tlin.com>,
Chris Packham <chris.packham@...iedtelesis.co.nz>, Andy Shevchenko <andy@...nel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>, Rob Herring <robh+dt@...nel.org>,
krzysztof.kozlowski+dt@...aro.org, Conor Dooley <conor+dt@...nel.org>,
Andrew Lunn <andrew@...n.ch>, Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Lee Jones <lee@...nel.org>, linux-leds@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 3/3] ARM: dts: marvell: Add 7-segment LED display on x530
On Fri, Mar 8, 2024 at 12:19 PM Arnd Bergmann <arnd@...nel.org> wrote:
> On Fri, Mar 8, 2024, at 10:56, Andy Shevchenko wrote:
> > On Fri, Mar 8, 2024 at 9:36 AM Gregory CLEMENT
> > <gregory.clement@...tlin.com> wrote:
> >> Chris Packham <chris.packham@...iedtelesis.co.nz> writes:
> >>
> >> > The Allied Telesis x530 products have a 7-segment LED display which is
> >> > used for node identification when the devices are stacked. Represent
> >> > this as a gpio-7-segment device.
> >> >
> >> > Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
> >>
> >> Acked-by: Gregory CLEMENT <gregory.clement@...tlin.com>
> >>
> >> Normally, this patch should be taken in mvebu and then merged by
> >> arm-soc. However, I haven't seen any other patch touching this file (so
> >> no risk of merge conflict) and I think it's too late for me to make a
> >> new pull request to arm-soc. So I'm not against it being taken with the
> >> rest of the patches. However, I think it would be a good idea to see
> >> what Arnd thinks about it.
> >
> > Arnd wasn't Cc'ed, now I added him.
>
> I already have a 'late' branch for stuff that for some reason
> was too late be part of the normal pull requests but should
> still make it into 6.9. If this one is important, I don't
> mind taking it.
>
> On the other hand, from the patch description this one doesn't
> seem that urgent, so I don't see much harm in delaying it
> to v6.10, and using the normal process for it.
Thanks, I will defer this one then.
Chris, please handle this one after v6.9-rc1 is out. The first two I'm
going to take today.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists