All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Jungclaus <frank.jungclaus@esd.eu>
To: linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>,
	Wolfgang Grandegger <wg@grandegger.com>,
	Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: "Stefan Mätje" <stefan.maetje@esd.eu>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Frank Jungclaus" <frank.jungclaus@esd.eu>
Subject: [PATCH 2/5] can/esd_usb: Add an entry to the MAINTAINERS file
Date: Fri, 24 Jun 2022 21:05:16 +0200	[thread overview]
Message-ID: <20220624190517.2299701-3-frank.jungclaus@esd.eu> (raw)
In-Reply-To: <20220624190517.2299701-1-frank.jungclaus@esd.eu>

As suggested by Marc, I added an entry for ESD CAN/USB Drivers
to the MAINTAINERS file

Signed-off-by: Frank Jungclaus <frank.jungclaus@esd.eu>
---
 MAINTAINERS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 05fcbea3e432..2d1cf1718140 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7406,6 +7406,13 @@ S:	Maintained
 F:	include/linux/errseq.h
 F:	lib/errseq.c
 
+ESD CAN/USB DRIVERS
+M:	Frank Jungclaus <frank.jungclaus@esd.eu>
+R:	socketcan@esd.eu
+L:	linux-can@vger.kernel.org
+S:	Maintained
+F:	drivers/net/can/usb/esd_usb.c
+
 ET131X NETWORK DRIVER
 M:	Mark Einon <mark.einon@gmail.com>
 S:	Odd Fixes
-- 
2.25.1


  parent reply	other threads:[~2022-06-24 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 19:05 [PATCH 0/5] Some preparation for supporting esd CAN-USB/3 Frank Jungclaus
2022-06-24 19:05 ` [PATCH 1/5] can/esd_usb2: Rename esd_usb2.c to esd_usb.c Frank Jungclaus
2022-06-24 19:05 ` Frank Jungclaus [this message]
2022-06-24 19:05 ` [PATCH 3/5] can/esd_usb: Rename all terms USB2 to USB Frank Jungclaus
2022-06-24 19:05 ` [PATCH 4/5] can/esd_usb: Fixed some checkpatch.pl warnings Frank Jungclaus
2022-06-24 19:05 ` [PATCH 5/5] can/esd_usb: Update to copyright, M_AUTHOR and M_DESCRIPTION Frank Jungclaus

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=20220624190517.2299701-3-frank.jungclaus@esd.eu \
    --to=frank.jungclaus@esd.eu \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=stefan.maetje@esd.eu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.