From: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>, u-boot@lists.denx.de
Cc: Michal Simek <michal.simek@amd.com>,
Tom Rini <trini@konsulko.com>,
Paul Burton <paulburton@kernel.org>,
Simon Glass <sjg@chromium.org>, Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Sumit Garg <sumit.garg@linaro.org>,
Jonas Karlman <jonas@kwiboo.se>
Subject: Re: [PATCH v3 12/12] mailmap: Update email for Paul Burton
Date: Sun, 19 May 2024 20:24:58 +0200 [thread overview]
Message-ID: <6efc687b-4aaa-4bf2-b705-303138cf330c@gmail.com> (raw)
In-Reply-To: <20240517-boston-v3-12-1ea7d23f4a1d@flygoat.com>
On 5/17/24 20:15, Jiaxun Yang wrote:
> Paul had left MIPS a couple of years ago, his email address is
> no longer valid.
>
> Replace it with his kenrel.org email, which has been used in
> kernel and QEMU, in case we still want to reach him.
>
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
> .mailmap | 3 ++-
> board/imgtec/boston/MAINTAINERS | 2 +-
> board/imgtec/malta/MAINTAINERS | 2 +-
> 3 files changed, 4 insertions(+), 3 deletions(-)
>
Reviewed-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
next prev parent reply other threads:[~2024-05-19 18:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 18:14 [PATCH v3 00/12] MIPS: Boston: Various enhancements Jiaxun Yang
2024-05-17 18:14 ` [PATCH v3 01/12] pci: xilinx: Handle size of ecam region properly Jiaxun Yang
2024-05-19 17:57 ` Daniel Schwierzeck
2024-05-17 18:14 ` [PATCH v3 02/12] pci: auto: Reduce bridge mem alignment boundary for boston Jiaxun Yang
2024-05-19 17:57 ` Daniel Schwierzeck
2024-05-17 18:14 ` [PATCH v3 03/12] pci: Enable PCI_MAP_SYSTEM_MEMORY when ARCH_MAP_SYSMEM is not set Jiaxun Yang
2024-05-19 17:58 ` Daniel Schwierzeck
2024-05-17 18:14 ` [PATCH v3 04/12] ahci: DMA addressing fixes Jiaxun Yang
2024-05-17 18:14 ` [PATCH v3 05/12] ahci: dwc_ahsata: Generalize the driver Jiaxun Yang
2024-05-17 18:14 ` [PATCH v3 06/12] MIPS: Provide dummy acpi_table.h Jiaxun Yang
2024-05-19 17:59 ` Daniel Schwierzeck
2024-05-17 18:14 ` [PATCH v3 07/12] MIPS: boston: Imply various options Jiaxun Yang
2024-05-19 17:59 ` Daniel Schwierzeck
2024-05-17 18:14 ` [PATCH v3 08/12] MIPS: boston: Provide default env vars Jiaxun Yang
2024-05-19 17:59 ` Daniel Schwierzeck
2024-05-17 18:14 ` [PATCH v3 09/12] clk: boston: Allow to get regmap from parent device Jiaxun Yang
2024-05-19 18:16 ` Daniel Schwierzeck
2024-05-17 18:14 ` [PATCH v3 10/12] dts/upstream: Add Makefile for MIPS Jiaxun Yang
2024-05-19 18:18 ` Daniel Schwierzeck
2024-05-17 18:14 ` [PATCH v3 11/12] MIPS: boston: Migrate to OF_UPSTREAM Jiaxun Yang
2024-05-19 18:20 ` Daniel Schwierzeck
2024-05-19 20:57 ` Jiaxun Yang
2024-05-19 22:47 ` Tom Rini
2024-05-20 9:52 ` Sumit Garg
2024-05-17 18:15 ` [PATCH v3 12/12] mailmap: Update email for Paul Burton Jiaxun Yang
2024-05-19 18:24 ` Daniel Schwierzeck [this message]
2024-05-30 19:21 ` Maciej W. Rozycki
2024-07-17 14:33 ` [PATCH v3 00/12] MIPS: Boston: Various enhancements Jiaxun Yang
2025-04-23 1:49 ` Tom Rini
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=6efc687b-4aaa-4bf2-b705-303138cf330c@gmail.com \
--to=daniel.schwierzeck@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=jonas@kwiboo.se \
--cc=lukma@denx.de \
--cc=michal.simek@amd.com \
--cc=paulburton@kernel.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=sumit.garg@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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