From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Arnd Bergmann <arnd@kernel.org>
Cc: Gregory Clement <gregory.clement@bootlin.com>,
Andy Shevchenko <andy@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Rob Herring <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Lee Jones <lee@kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 3/3] ARM: dts: marvell: Add 7-segment LED display on x530
Date: Sun, 10 Mar 2024 20:22:01 +0000 [thread overview]
Message-ID: <6c3451ed-6346-45e2-940e-851cb99a1b63@alliedtelesis.co.nz> (raw)
In-Reply-To: <CAHp75VfiaWFricM4Or771P0LJVoFoEmQtoJo1hySo=BRS-59DQ@mail.gmail.com>
On 8/03/24 23:34, Andy Shevchenko wrote:
> On Fri, Mar 8, 2024 at 12:19 PM Arnd Bergmann <arnd@kernel.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@bootlin.com> wrote:
>>>> Chris Packham <chris.packham@alliedtelesis.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@alliedtelesis.co.nz>
>>>> Acked-by: Gregory CLEMENT <gregory.clement@bootlin.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.
>
No problem. I can send the dts changes separately.
FYI ./scripts/get_maintainer.pl -f arch/arm/boot/dts/marvell isn't
picking up Arnd should it?
next prev parent reply other threads:[~2024-03-10 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 23:50 [PATCH v5 0/3] auxdisplay: 7-segment LED display Chris Packham
2024-03-06 23:50 ` [PATCH v5 1/3] auxdisplay: Add 7-segment LED display driver Chris Packham
2024-03-07 13:13 ` Geert Uytterhoeven
2024-03-07 13:23 ` Andy Shevchenko
2024-03-06 23:50 ` [PATCH v5 2/3] dt-bindings: auxdisplay: Add bindings for generic 7-segment LED Chris Packham
2024-03-07 13:11 ` Geert Uytterhoeven
2024-03-07 14:52 ` Rob Herring
2024-03-06 23:50 ` [PATCH v5 3/3] ARM: dts: marvell: Add 7-segment LED display on x530 Chris Packham
2024-03-08 7:36 ` Gregory CLEMENT
2024-03-08 9:56 ` Andy Shevchenko
2024-03-08 10:18 ` Arnd Bergmann
2024-03-08 10:34 ` Andy Shevchenko
2024-03-10 20:22 ` Chris Packham [this message]
2024-03-11 6:02 ` Arnd Bergmann
2024-03-11 19:54 ` Chris Packham
2024-03-07 12:07 ` [PATCH v5 0/3] auxdisplay: 7-segment LED display Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c3451ed-6346-45e2-940e-851cb99a1b63@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=arnd@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).