LKML Archive on
help / color / mirror / Atom feed
From: "Stefan Mätje" <>
To: "" <>
Cc: "" <>,
	"" <>
Subject: Re: [PATCH] mailmap: update email address of Matthias Fuchs
Date: Mon, 9 Aug 2021 17:22:51 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Am Montag, den 09.08.2021, 09:24 +0200 schrieb Marc Kleine-Budde:
> On 06.08.2021 15:07:43, Stefan Mätje wrote:
> > I was not aware of the .mailmap file and its workings. 
> The mailmap file works on the git log, and thus tools using it: e.g.
> scripts/
> > My question is should then also <> be put in this
> > file
> Probably yes, as there are two patches by him in the Linux kernel:
> > Thomas Körper (2):
> >       can: dev: avoid calling kfree_skb() from interrupt context
> >       can: esd_usb2: Fix sparse warnings
> I'll update this patch.
> > because he is the co-author of the patch you're reviewing atm.
> For co-authorship, use the Co-developed-by tag, that was recently added:

I will do that.

> Speaking of that patch. Can you please create an entry in the
> MAINTAINERS file, too? I suggest to add yourself as M: and the
> socketcan@e.u as R:. The change in the MAINTAINERS file will be a second
> patch in that series. Just include it the next iteration of that series.

Do you think of something like the patch below? I'm curious. Shouldn't there 
be similar entries for the drivers from Vincent (drivers/net/can/usb/etas_es58x/)
and the PEAK driver family (drivers/net/can/peak_canfd/)? Why are they not there?
Have I misunderstood something?

index 41fcfdb24a81..f25e3f79b392 100644
@@ -4111,6 +4111,14 @@ F:       include/uapi/linux/can/error.h
 F:     include/uapi/linux/can/netlink.h
 F:     include/uapi/linux/can/vxcan.h
+M:     Stefan Mätje <>
+S:     Maintained
+F:     drivers/net/can/esd/
+F:     drivers/net/can/usb/esd_usb2.c
 M:     Oliver Hartkopp <>
 M:     Marc Kleine-Budde <>

> > and his email address shows up in MODULE_AUTHOR() macro. He also left
> > our company already.
> In newly added changes, it makes sense that all email addresses are
> working. :D

So I'll remove his stale email address together with the MODULE_AUTHOR() macro
and file the authorship credits in a changed copyright history at the top of
the source files.

Best regards,

  reply	other threads:[~2021-08-09 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 10:48 [PATCH] mailmap: update email address of Matthias Fuchs Marc Kleine-Budde
2021-08-06 15:07 ` Stefan Mätje
2021-08-09  7:24   ` Marc Kleine-Budde
2021-08-09 17:22     ` Stefan Mätje [this message]
2021-08-09 17:51       ` Marc Kleine-Budde
2021-08-12 13:27         ` Stefan Mätje
2021-08-12 13:39           ` Marc Kleine-Budde
2021-08-09 17:44 ` Joe Perches
2021-08-09 17:59   ` Marc Kleine-Budde

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).