From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: michael.riesch@collabora.com,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Fabio Estevam" <festevam@gmail.com>
Cc: Collabora Kernel Team <kernel@collabora.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] mailmap: add entry for Michael Riesch
Date: Mon, 14 Apr 2025 08:42:31 -0400 [thread overview]
Message-ID: <cffb6a6448a0cb32cc7b13e3048c097b3efc6f93.camel@collabora.com> (raw)
In-Reply-To: <9f1c7c30082de242b4906e5ecbeb382400fcd4a2.camel@collabora.com>
Le vendredi 11 avril 2025 à 17:25 -0400, Nicolas Dufresne a écrit :
> Le jeudi 10 avril 2025 à 21:41 +0200, Michael Riesch via B4 Relay a
> écrit :
> > From: Michael Riesch <michael.riesch@collabora.com>
> >
> > After five interesting years, I left WolfVision and started to work
> > for
> > Collabora. Add a corresponding mailmap entry.
> >
> > Signed-off-by: Michael Riesch <michael.riesch@collabora.com>
>
> Reviewed-by: Nicolas Dufresne <nicolas.collabora@collabora.com>
Friday's typo special:
nicolas.dufresne@collabora.com
:-(
Nicolas
>
> > ---
> > .mailmap | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/.mailmap b/.mailmap
> > index 4f7cd8e23177..59f99aa83185 100644
> > --- a/.mailmap
> > +++ b/.mailmap
> > @@ -503,6 +503,7 @@ Mayuresh Janorkar <mayur@ti.com>
> > Md Sadre Alam <quic_mdalam@quicinc.com> <mdalam@codeaurora.org>
> > Miaoqing Pan <quic_miaoqing@quicinc.com> <miaoqing@codeaurora.org>
> > Michael Buesch <m@bues.ch>
> > +Michael Riesch <michael.riesch@collabora.com>
> > <michael.riesch@wolfvision.net>
> > Michal Simek <michal.simek@amd.com> <michal.simek@xilinx.com>
> > Michel Dänzer <michel@tungstengraphics.com>
> > Michel Lespinasse <michel@lespinasse.org>
next prev parent reply other threads:[~2025-04-14 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 19:41 [PATCH 0/3] update e-mail address for Michael Riesch Michael Riesch via B4 Relay
2025-04-10 19:41 ` [PATCH 1/3] MAINTAINERS: add exclude for dt-bindings to imx entry Michael Riesch via B4 Relay
2025-04-14 9:17 ` Sakari Ailus
2025-04-25 1:36 ` Shawn Guo
2025-04-10 19:41 ` [PATCH 2/3] mailmap: add entry for Michael Riesch Michael Riesch via B4 Relay
2025-04-11 21:25 ` Nicolas Dufresne
2025-04-14 12:42 ` Nicolas Dufresne [this message]
2025-04-10 19:41 ` [PATCH 3/3] media: dt-bindings: sony,imx415: update maintainer e-mail address Michael Riesch via B4 Relay
2025-04-11 18:05 ` Rob Herring (Arm)
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=cffb6a6448a0cb32cc7b13e3048c097b3efc6f93.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@collabora.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michael.riesch@collabora.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sakari.ailus@linux.intel.com \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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