On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
> From: Jason Li <[email protected]>
>
> Convert the Cortina-Access UART binding to DT schema format.
>
> Signed-off-by: Jason Li <[email protected]>
> ---
> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> MAINTAINERS | 6 +++
You are also adding a MAINTAINERS entry here, which is not listed in the
changelog text, so I couldn't take it anyway :(
greg k-h
MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
thus not sure what we could at to Changelog which would add value or clarity for others
from the v1.
> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
>
> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
>> From: Jason Li <[email protected]>
>>
>> Convert the Cortina-Access UART binding to DT schema format.
>>
>> Signed-off-by: Jason Li <[email protected]>
>> ---
>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>> MAINTAINERS | 6 +++
>
> You are also adding a MAINTAINERS entry here, which is not listed in the
> changelog text, so I couldn't take it anyway :(
>
> greg k-h
On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
> thus not sure what we could at to Changelog which would add value or clarity for others
> from the v1.
>
> > On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
> >
> > On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
> >> From: Jason Li <[email protected]>
> >>
> >> Convert the Cortina-Access UART binding to DT schema format.
> >>
> >> Signed-off-by: Jason Li <[email protected]>
> >> ---
> >> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
> >> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> >> MAINTAINERS | 6 +++
> >
> > You are also adding a MAINTAINERS entry here, which is not listed in the
> > changelog text, so I couldn't take it anyway :(
Add the maintainers entry in the first patch, with the driver please.
> On Jun 15, 2021, at 7:13 AM, Greg Kroah-Hartman <[email protected]> wrote:
>
> On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
>> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
>> thus not sure what we could at to Changelog which would add value or clarity for others
>> from the v1.
>>
>>> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
>>>
>>> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
>>>> From: Jason Li <[email protected]>
>>>>
>>>> Convert the Cortina-Access UART binding to DT schema format.
>>>>
>>>> Signed-off-by: Jason Li <[email protected]>
>>>> ---
>>>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
>>>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>>>> MAINTAINERS | 6 +++
>>>
>>> You are also adding a MAINTAINERS entry here, which is not listed in the
>>> changelog text, so I couldn't take it anyway :(
>
> Add the maintainers entry in the first patch, with the driver please.
The change to MAINTAINERS here add a new file into the DT documentation.
Should it not be grouped into the dt-binding portion and reviewed by the DT time for which this patch
is CC’ed to? Why would moving the DT documentation file that is introduced be into the first patch, which is the
serial driver itself be the correct approach?
On Tue, Jun 15, 2021 at 02:39:08PM +0000, Alex Nemirovsky wrote:
>
>
> > On Jun 15, 2021, at 7:13 AM, Greg Kroah-Hartman <[email protected]> wrote:
> >
> > On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
> >> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
> >> thus not sure what we could at to Changelog which would add value or clarity for others
> >> from the v1.
> >>
> >>> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
> >>>
> >>> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
> >>>> From: Jason Li <[email protected]>
> >>>>
> >>>> Convert the Cortina-Access UART binding to DT schema format.
> >>>>
> >>>> Signed-off-by: Jason Li <[email protected]>
> >>>> ---
> >>>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
> >>>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> >>>> MAINTAINERS | 6 +++
> >>>
> >>> You are also adding a MAINTAINERS entry here, which is not listed in the
> >>> changelog text, so I couldn't take it anyway :(
> >
> > Add the maintainers entry in the first patch, with the driver please.
>
> The change to MAINTAINERS here add a new file into the DT documentation.
> Should it not be grouped into the dt-binding portion and reviewed by the DT time for which this patch
> is CC’ed to? Why would moving the DT documentation file that is introduced be into the first patch, which is the
> serial driver itself be the correct approach?
Add it as a stand-alone patch at the end of the series, that just adds
the MAINTAINERS entry.
thanks,
greg k-h
On Tue, Jun 15, 2021 at 8:39 AM Alex Nemirovsky
<[email protected]> wrote:
>
>
>
> > On Jun 15, 2021, at 7:13 AM, Greg Kroah-Hartman <[email protected]> wrote:
> >
> > On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
> >> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
> >> thus not sure what we could at to Changelog which would add value or clarity for others
> >> from the v1.
> >>
> >>> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
> >>>
> >>> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
> >>>> From: Jason Li <[email protected]>
> >>>>
> >>>> Convert the Cortina-Access UART binding to DT schema format.
> >>>>
> >>>> Signed-off-by: Jason Li <[email protected]>
> >>>> ---
> >>>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
> >>>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> >>>> MAINTAINERS | 6 +++
> >>>
> >>> You are also adding a MAINTAINERS entry here, which is not listed in the
> >>> changelog text, so I couldn't take it anyway :(
> >
> > Add the maintainers entry in the first patch, with the driver please.
>
> The change to MAINTAINERS here add a new file into the DT documentation.
> Should it not be grouped into the dt-binding portion and reviewed by the DT time for which this patch
> is CC’ed to? Why would moving the DT documentation file that is introduced be into the first patch, which is the
> serial driver itself be the correct approach?
The binding doesn't actually need a MAINTAINERS entry (though having
one is fine). get_maintainers.pl will also pull emails from the
binding schema.
Rob
> On Jun 15, 2021, at 8:44 AM, Rob Herring <[email protected]> wrote:
>
> On Tue, Jun 15, 2021 at 8:39 AM Alex Nemirovsky
> <[email protected]> wrote:
>>
>>
>>
>>> On Jun 15, 2021, at 7:13 AM, Greg Kroah-Hartman <[email protected]> wrote:
>>>
>>> On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
>>>> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
>>>> thus not sure what we could at to Changelog which would add value or clarity for others
>>>> from the v1.
>>>>
>>>>> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
>>>>>
>>>>> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
>>>>>> From: Jason Li <[email protected]>
>>>>>>
>>>>>> Convert the Cortina-Access UART binding to DT schema format.
>>>>>>
>>>>>> Signed-off-by: Jason Li <[email protected]>
>>>>>> ---
>>>>>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
>>>>>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>>>>>> MAINTAINERS | 6 +++
>>>>>
>>>>> You are also adding a MAINTAINERS entry here, which is not listed in the
>>>>> changelog text, so I couldn't take it anyway :(
>>>
>>> Add the maintainers entry in the first patch, with the driver please.
>>
>> The change to MAINTAINERS here add a new file into the DT documentation.
>> Should it not be grouped into the dt-binding portion and reviewed by the DT time for which this patch
>> is CC’ed to? Why would moving the DT documentation file that is introduced be into the first patch, which is the
>> serial driver itself be the correct approach?
>
> The binding doesn't actually need a MAINTAINERS entry (though having
> one is fine). get_maintainers.pl will also pull emails from the
> binding schema.
>
> Rob
Hi Rob,
It sounds like you are find with patch 2/3 from a DT point of view. Could we review the rest from the DT point of view
to get either feedback for changes or ACK these, so we can unblock this series?
Thanks
Alex
On Tue, Jun 15, 2021 at 10:06 AM Alex Nemirovsky
<[email protected]> wrote:
>
>
>
> > On Jun 15, 2021, at 8:44 AM, Rob Herring <[email protected]> wrote:
> >
> > On Tue, Jun 15, 2021 at 8:39 AM Alex Nemirovsky
> > <[email protected]> wrote:
> >>
> >>
> >>
> >>> On Jun 15, 2021, at 7:13 AM, Greg Kroah-Hartman <[email protected]> wrote:
> >>>
> >>> On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
> >>>> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
> >>>> thus not sure what we could at to Changelog which would add value or clarity for others
> >>>> from the v1.
> >>>>
> >>>>> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
> >>>>>
> >>>>> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
> >>>>>> From: Jason Li <[email protected]>
> >>>>>>
> >>>>>> Convert the Cortina-Access UART binding to DT schema format.
> >>>>>>
> >>>>>> Signed-off-by: Jason Li <[email protected]>
> >>>>>> ---
> >>>>>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
> >>>>>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> >>>>>> MAINTAINERS | 6 +++
> >>>>>
> >>>>> You are also adding a MAINTAINERS entry here, which is not listed in the
> >>>>> changelog text, so I couldn't take it anyway :(
> >>>
> >>> Add the maintainers entry in the first patch, with the driver please.
> >>
> >> The change to MAINTAINERS here add a new file into the DT documentation.
> >> Should it not be grouped into the dt-binding portion and reviewed by the DT time for which this patch
> >> is CC’ed to? Why would moving the DT documentation file that is introduced be into the first patch, which is the
> >> serial driver itself be the correct approach?
> >
> > The binding doesn't actually need a MAINTAINERS entry (though having
> > one is fine). get_maintainers.pl will also pull emails from the
> > binding schema.
> >
> > Rob
>
> Hi Rob,
> It sounds like you are find with patch 2/3 from a DT point of view. Could we review the rest from the DT point of view
> to get either feedback for changes or ACK these, so we can unblock this series?
Can't say I've seen it as I only see replies in my mail. Did this
originally go to the DT list? If not, it's never in my queue[1].
Rob
[1] https://patchwork.ozlabs.org/project/devicetree-bindings/list/
On Tue, Jun 15, 2021 at 6:21 PM Rob Herring <[email protected]> wrote:
> On Tue, Jun 15, 2021 at 10:06 AM Alex Nemirovsky
> <[email protected]> wrote:
> > > On Jun 15, 2021, at 8:44 AM, Rob Herring <[email protected]> wrote:
> > > On Tue, Jun 15, 2021 at 8:39 AM Alex Nemirovsky
> > > <[email protected]> wrote:
> > >>
> > >>
> > >>
> > >>> On Jun 15, 2021, at 7:13 AM, Greg Kroah-Hartman <[email protected]> wrote:
> > >>>
> > >>> On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
> > >>>> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
> > >>>> thus not sure what we could at to Changelog which would add value or clarity for others
> > >>>> from the v1.
> > >>>>
> > >>>>> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
> > >>>>>
> > >>>>> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
> > >>>>>> From: Jason Li <[email protected]>
> > >>>>>>
> > >>>>>> Convert the Cortina-Access UART binding to DT schema format.
> > >>>>>>
> > >>>>>> Signed-off-by: Jason Li <[email protected]>
> > >>>>>> ---
> > >>>>>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
> > >>>>>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> > >>>>>> MAINTAINERS | 6 +++
> > >>>>>
> > >>>>> You are also adding a MAINTAINERS entry here, which is not listed in the
> > >>>>> changelog text, so I couldn't take it anyway :(
> > >>>
> > >>> Add the maintainers entry in the first patch, with the driver please.
> > >>
> > >> The change to MAINTAINERS here add a new file into the DT documentation.
> > >> Should it not be grouped into the dt-binding portion and reviewed by the DT time for which this patch
> > >> is CC’ed to? Why would moving the DT documentation file that is introduced be into the first patch, which is the
> > >> serial driver itself be the correct approach?
> > >
> > > The binding doesn't actually need a MAINTAINERS entry (though having
> > > one is fine). get_maintainers.pl will also pull emails from the
> > > binding schema.
> > >
> > > Rob
> >
> > Hi Rob,
> > It sounds like you are find with patch 2/3 from a DT point of view. Could we review the rest from the DT point of view
> > to get either feedback for changes or ACK these, so we can unblock this series?
>
> Can't say I've seen it as I only see replies in my mail. Did this
> originally go to the DT list? If not, it's never in my queue[1].
>
> Rob
>
> [1] https://patchwork.ozlabs.org/project/devicetree-bindings/list/
None of the patches in this series ended up on a mailing list or on
lore, so no one could comment on them, except for people CCed directly.
The driver has been accepted in tty-next, commit b61c8bf4694b5115
("tty: serial: Add UART driver for Cortina-Access platform"). From a
quick glance, it could have used some review.
The driver is using the compatible value "cortina-access,serial", so I
guess the binding patch added "cortina-access" to vendor-prefixes.yaml.
According to https://www.cortina-access.com/news-and-events, this is
the same company as Cortina Systems, which already has the "cortina"
vendor prefix. In 2015, it was acquired by Realtek, so perhaps it
should use the "realtek" prefix instead for new development?
The SERIAL_CORTINA_ACCESS symbol doesn't depend on anything, so
it will show up on everyone's oldconfig radar soon, regardless of
building a kernel for a Cortina Access system or not.
I wanted to change it to something like:
config SERIAL_CORTINA_ACCESS
tristate "Cortina-Access serial port support"
+ depends on FIXME || COMPILE_TEST
select SERIAL_CORE
help
This driver is for Cortina-Access SoC's UART. If you
have a machine
based on the Cortina-Access SoC and wish to use the serial port,
say 'Y' here. Otherwise, say 'N'.
but given there is no evidence of patches to add support for the
CAXXXX line of SoCs, there's no symbol to depend on...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
This is NOT the same company as Cortina Systems and is NOT Realtek. It’s is it’s own entity and does not have the right to use the Cortina Systems name with is owned by a different company.
> On Jun 22, 2021, at 4:28 AM, Geert Uytterhoeven <[email protected]> wrote:
>
> On Tue, Jun 15, 2021 at 6:21 PM Rob Herring <[email protected]> wrote:
>> On Tue, Jun 15, 2021 at 10:06 AM Alex Nemirovsky
>> <[email protected]> wrote:
>>>> On Jun 15, 2021, at 8:44 AM, Rob Herring <[email protected]> wrote:
>>>> On Tue, Jun 15, 2021 at 8:39 AM Alex Nemirovsky
>>>> <[email protected]> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> On Jun 15, 2021, at 7:13 AM, Greg Kroah-Hartman <[email protected]> wrote:
>>>>>>
>>>>>> On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
>>>>>>> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
>>>>>>> thus not sure what we could at to Changelog which would add value or clarity for others
>>>>>>> from the v1.
>>>>>>>
>>>>>>>> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
>>>>>>>>
>>>>>>>>> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
>>>>>>>>>> From: Jason Li <[email protected]>
>>>>>>>>>>
>>>>>>>>>> Convert the Cortina-Access UART binding to DT schema format.
>>>>>>>>>>
>>>>>>>>>> Signed-off-by: Jason Li <[email protected]>
>>>>>>>>>> ---
>>>>>>>>>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
>>>>>>>>>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>>>>>>>>>> MAINTAINERS | 6 +++
>>>>>>>>>
>>>>>>>>> You are also adding a MAINTAINERS entry here, which is not listed in the
>>>>>>>>> changelog text, so I couldn't take it anyway :(
>>>>>>>
>>>>>>> Add the maintainers entry in the first patch, with the driver please.
>>>>>>
>>>>>> The change to MAINTAINERS here add a new file into the DT documentation.
>>>>>> Should it not be grouped into the dt-binding portion and reviewed by the DT time for which this patch
>>>>>> is CC’ed to? Why would moving the DT documentation file that is introduced be into the first patch, which is the
>>>>>> serial driver itself be the correct approach?
>>>>>
>>>>> The binding doesn't actually need a MAINTAINERS entry (though having
>>>>> one is fine). get_maintainers.pl will also pull emails from the
>>>>> binding schema.
>>>>>
>>>>> Rob
>>>
>>> Hi Rob,
>>> It sounds like you are find with patch 2/3 from a DT point of view. Could we review the rest from the DT point of view
>>> to get either feedback for changes or ACK these, so we can unblock this series?
>>
>> Can't say I've seen it as I only see replies in my mail. Did this
>> originally go to the DT list? If not, it's never in my queue[1].
>>
>> Rob
>>
>> [1] https://patchwork.ozlabs.org/project/devicetree-bindings/list/
>
> None of the patches in this series ended up on a mailing list or on
> lore, so no one could comment on them, except for people CCed directly.
>
> The driver has been accepted in tty-next, commit b61c8bf4694b5115
> ("tty: serial: Add UART driver for Cortina-Access platform"). From a
> quick glance, it could have used some review.
>
> The driver is using the compatible value "cortina-access,serial", so I
> guess the binding patch added "cortina-access" to vendor-prefixes.yaml.
> According to https://www.cortina-access.com/news-and-events, this is
> the same company as Cortina Systems, which already has the "cortina"
> vendor prefix. In 2015, it was acquired by Realtek, so perhaps it
> should use the "realtek" prefix instead for new development?
>
> The SERIAL_CORTINA_ACCESS symbol doesn't depend on anything, so
> it will show up on everyone's oldconfig radar soon, regardless of
> building a kernel for a Cortina Access system or not.
> I wanted to change it to something like:
>
> config SERIAL_CORTINA_ACCESS
> tristate "Cortina-Access serial port support"
> + depends on FIXME || COMPILE_TEST
> select SERIAL_CORE
> help
> This driver is for Cortina-Access SoC's UART. If you
> have a machine
> based on the Cortina-Access SoC and wish to use the serial port,
> say 'Y' here. Otherwise, say 'N'.
>
> but given there is no evidence of patches to add support for the
> CAXXXX line of SoCs, there's no symbol to depend on...
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
On Tue, Jun 22, 2021 at 1:29 PM Geert Uytterhoeven <[email protected]> wrote:
> On Tue, Jun 15, 2021 at 6:21 PM Rob Herring <[email protected]> wrote:
> > On Tue, Jun 15, 2021 at 10:06 AM Alex Nemirovsky <[email protected]> wrote:
> > > It sounds like you are find with patch 2/3 from a DT point of view. Could we review the rest from the DT point of view
> > > to get either feedback for changes or ACK these, so we can unblock this series?
> >
> > Can't say I've seen it as I only see replies in my mail. Did this
> > originally go to the DT list? If not, it's never in my queue[1].
>
> None of the patches in this series ended up on a mailing list or on
> lore, so no one could comment on them, except for people CCed directly.
Right, in fact every email I see from @cortina-access.com at
https://lore.kernel.org/lkml/?q=cortina-access.com is a reply, but the
original mails are all missing, not just this series.
It appears that there is a problem between the mail servers of cortina-access
and kernel.org. Alex and Jason, please double-check if you find
anything in
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
https://www.kernel.org/doc/html/latest/process/email-clients.html
that may have caused this on your end, or otherwise contact
[email protected] for help.
> The driver has been accepted in tty-next, commit b61c8bf4694b5115
> ("tty: serial: Add UART driver for Cortina-Access platform"). From a
> quick glance, it could have used some review.
>
> The driver is using the compatible value "cortina-access,serial", so I
> guess the binding patch added "cortina-access" to vendor-prefixes.yaml.
Ah right. That patch has not made it in because of the issue, but right
away I can tell that the binding is not great because the compatible
string is way too generic: it implies that cortina-access only uses a single
serial port type in every past, present or future SoC, which is clearly
not the case.
It's obviously up to Greg to decide whether to revert the patch, but
I'd suggest we don't treat the driver as conforming to the binding until
it has been reviewed, and assume that changes will be made.
> The SERIAL_CORTINA_ACCESS symbol doesn't depend on anything, so
> it will show up on everyone's oldconfig radar soon, regardless of
> building a kernel for a Cortina Access system or not.
> I wanted to change it to something like:
>
> config SERIAL_CORTINA_ACCESS
> tristate "Cortina-Access serial port support"
> + depends on FIXME || COMPILE_TEST
> select SERIAL_CORE
> help
> This driver is for Cortina-Access SoC's UART. If you
> have a machine
> based on the Cortina-Access SoC and wish to use the serial port,
> say 'Y' here. Otherwise, say 'N'.
>
> but given there is no evidence of patches to add support for the
> CAXXXX line of SoCs, there's no symbol to depend on...
Assuming this is a SoC based on an Arm CPU core, it's clear that
nothing from cortina-access.com ever made it through the
[email protected] mailing list either, if anything
was sent at all.
Alex, please try to contact me off-list about merging the full SoC
support, I should be able to help you come up with a plan for
submitting the rest as soon as the email troubles are resolved.
For new Arm based SoC platforms, arch/{arm,arm64} patches
should go through the soc tree and be picked up by Olof (on Cc)
or me. The exact process is not well documented, but please
contact us by email, or on irc://irc.libera.chat/#armlinux if you
have questions.
Arnd
On Tue, Jun 22, 2021 at 01:28:06PM +0200, Geert Uytterhoeven wrote:
> On Tue, Jun 15, 2021 at 6:21 PM Rob Herring <[email protected]> wrote:
> > On Tue, Jun 15, 2021 at 10:06 AM Alex Nemirovsky
> > <[email protected]> wrote:
> > > > On Jun 15, 2021, at 8:44 AM, Rob Herring <[email protected]> wrote:
> > > > On Tue, Jun 15, 2021 at 8:39 AM Alex Nemirovsky
> > > > <[email protected]> wrote:
> > > >>
> > > >>
> > > >>
> > > >>> On Jun 15, 2021, at 7:13 AM, Greg Kroah-Hartman <[email protected]> wrote:
> > > >>>
> > > >>> On Tue, Jun 15, 2021 at 01:36:39PM +0000, Alex Nemirovsky wrote:
> > > >>>> MAINTAINERS modification was made in the initial version 1. We made no changes to it since then,
> > > >>>> thus not sure what we could at to Changelog which would add value or clarity for others
> > > >>>> from the v1.
> > > >>>>
> > > >>>>> On Jun 15, 2021, at 4:53 AM, Greg Kroah-Hartman <[email protected]> wrote:
> > > >>>>>
> > > >>>>> On Sun, May 09, 2021 at 11:45:17AM -0700, Alex Nemirovsky wrote:
> > > >>>>>> From: Jason Li <[email protected]>
> > > >>>>>>
> > > >>>>>> Convert the Cortina-Access UART binding to DT schema format.
> > > >>>>>>
> > > >>>>>> Signed-off-by: Jason Li <[email protected]>
> > > >>>>>> ---
> > > >>>>>> .../serial/cortina-access,serial.yaml | 46 +++++++++++++++++++
> > > >>>>>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> > > >>>>>> MAINTAINERS | 6 +++
> > > >>>>>
> > > >>>>> You are also adding a MAINTAINERS entry here, which is not listed in the
> > > >>>>> changelog text, so I couldn't take it anyway :(
> > > >>>
> > > >>> Add the maintainers entry in the first patch, with the driver please.
> > > >>
> > > >> The change to MAINTAINERS here add a new file into the DT documentation.
> > > >> Should it not be grouped into the dt-binding portion and reviewed by the DT time for which this patch
> > > >> is CC’ed to? Why would moving the DT documentation file that is introduced be into the first patch, which is the
> > > >> serial driver itself be the correct approach?
> > > >
> > > > The binding doesn't actually need a MAINTAINERS entry (though having
> > > > one is fine). get_maintainers.pl will also pull emails from the
> > > > binding schema.
> > > >
> > > > Rob
> > >
> > > Hi Rob,
> > > It sounds like you are find with patch 2/3 from a DT point of view. Could we review the rest from the DT point of view
> > > to get either feedback for changes or ACK these, so we can unblock this series?
> >
> > Can't say I've seen it as I only see replies in my mail. Did this
> > originally go to the DT list? If not, it's never in my queue[1].
> >
> > Rob
> >
> > [1] https://patchwork.ozlabs.org/project/devicetree-bindings/list/
>
> None of the patches in this series ended up on a mailing list or on
> lore, so no one could comment on them, except for people CCed directly.
Ugh, I never noticed that I as I just applied one patch of the series,
my fault. I'll go revert them from my tree now...
thanks,
greg k-h