From: "Stefan Mätje" <Stefan.Maetje@esd.eu>
To: "vincent.mailhol@gmail.com" <vincent.mailhol@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"wg@grandegger.com" <wg@grandegger.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"mkl@pengutronix.de" <mkl@pengutronix.de>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH v10 1/2] MAINTAINERS: add Stefan Mätje as maintainer for the esd electronics GmbH PCIe/402 CAN drivers
Date: Wed, 22 Nov 2023 15:57:27 +0000 [thread overview]
Message-ID: <3148df93275530977d74a51aeda0c3bf59b71625.camel@esd.eu> (raw)
In-Reply-To: <CAMZ6RqKBDfX3qnJ8pMnQ55JFDFgGCQEQhNVGPXJKiGNvvBWXdQ@mail.gmail.com>
Am Mittwoch, den 22.11.2023, 00:02 +0900 schrieb Vincent Mailhol:
> On Tue. 21 Nov. 2023 at 02:57, Stefan Mätje <stefan.maetje@esd.eu> wrote:
> > Adding myself (Stefan Mätje) as a maintainer for the upcoming driver of
> > the PCIe/402 interface card family.
> >
> > Signed-off-by: Stefan Mätje <stefan.maetje@esd.eu>
> > ---
> > MAINTAINERS | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 03011d7ee087..7db1bd399822 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -7753,6 +7753,13 @@ L: linux-can@vger.kernel.org
> > S: Maintained
> > F: drivers/net/can/usb/esd_usb.c
> >
> > +ESD CAN NETWORK DRIVERS
> > +M: Stefan Mätje <stefan.maetje@esd.eu>
> > +R: socketcan@esd.eu
> > +L: linux-can@vger.kernel.org
> > +S: Maintained
> > +F: drivers/net/can/esd/
>
> The MAINTAINERS file should be kept in alphabetical order.
>
> So, maybe
>
> ESD CAN NETWORK DRIVERS
>
> goes before
>
> ESD CAN/USB DRIVERS
>
> ?
I'll change the order.
>
>
> At least, looking at the existing,
>
> ARM SUB-ARCHITECTURES
>
> is before:
>
> ARM/ACTIONS SEMI ARCHITECTURE
>
>
> > ET131X NETWORK DRIVER
> > M: Mark Einon <mark.einon@gmail.com>
> > S: Odd Fixes
> > --
> > 2.34.1
> >
> >
next prev parent reply other threads:[~2023-11-22 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 17:56 [PATCH v10 0/2] can: esd: add support for esd GmbH PCIe/402 CAN interface Stefan Mätje
2023-11-20 17:56 ` [PATCH v10 1/2] MAINTAINERS: add Stefan Mätje as maintainer for the esd electronics GmbH PCIe/402 CAN drivers Stefan Mätje
2023-11-21 15:02 ` Vincent Mailhol
2023-11-22 15:57 ` Stefan Mätje [this message]
2023-11-20 17:56 ` [PATCH v10 2/2] can: esd: add support for esd GmbH PCIe/402 CAN interface family Stefan Mätje
2023-11-21 15:04 ` Vincent Mailhol
2023-11-22 15:39 ` Stefan Mätje
2023-11-21 15:04 ` [PATCH v10 0/2] can: esd: add support for esd GmbH PCIe/402 CAN interface Vincent Mailhol
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=3148df93275530977d74a51aeda0c3bf59b71625.camel@esd.eu \
--to=stefan.maetje@esd.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vincent.mailhol@gmail.com \
--cc=wg@grandegger.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 read-only IMAP folder(s) and NNTP newsgroup(s).