All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Benjamin Poirier <benjamin.poirier@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Bjorn Andersson <quic_bjorande@quicinc.com>,
	Oleksij Rempel <o.rempel@pengutronix.de>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH] .mailmap: Map Benjamin Poirier's address
Date: Mon, 30 Oct 2023 21:24:55 +0700	[thread overview]
Message-ID: <20231030142454.22127-2-bagasdotme@gmail.com> (raw)

Map out to his gmail address as he had left SUSE some time ago.

Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
 I first contacted him when reporting tx-nocache-copy regression [1],
 I emailed to his old SUSE address, but bounces. Now, he submitted
 qlqe removal [2] using his gmail address.

 Ben, can you give an ACK? I intend to route this patch through mm or
 driver-core tree.

 [1]: https://lore.kernel.org/lkml/2bf06faa-a0a7-4dee-90cd-a054b4e4c947@gmail.com/
 [2]: https://lore.kernel.org/lkml/20231020124457.312449-1-benjamin.poirier@gmail.com/

 .mailmap | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.mailmap b/.mailmap
index 2643b7203a7452..34103d66c0372f 100644
--- a/.mailmap
+++ b/.mailmap
@@ -95,6 +95,7 @@ Ben M Cahill <ben.m.cahill@intel.com>
 Ben Widawsky <bwidawsk@kernel.org> <ben@bwidawsk.net>
 Ben Widawsky <bwidawsk@kernel.org> <ben.widawsky@intel.com>
 Ben Widawsky <bwidawsk@kernel.org> <benjamin.widawsky@intel.com>
+Benjamin Poirier <benjamin.poirier@gmail.com> <bpoirier@suse.de>
 Bjorn Andersson <andersson@kernel.org> <bjorn@kryo.se>
 Bjorn Andersson <andersson@kernel.org> <bjorn.andersson@linaro.org>
 Bjorn Andersson <andersson@kernel.org> <bjorn.andersson@sonymobile.com>

base-commit: ffc253263a1375a65fa6c9f62a893e9767fbebfa
-- 
An old man doll... just what I always wanted! - Clara


             reply	other threads:[~2023-10-30 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 14:24 Bagas Sanjaya [this message]
2023-10-30 14:49 ` [PATCH] .mailmap: Map Benjamin Poirier's address Benjamin Poirier

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=20231030142454.22127-2-bagasdotme@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=benjamin.poirier@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=konrad.dybcio@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=o.rempel@pengutronix.de \
    --cc=quic_bjorande@quicinc.com \
    --cc=stephen@networkplumber.org \
    /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.