Linux MM tree latest commits
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,radhey.shyam.pandey@amd.com,
	michal.simek@amd.com,jeff.johnson@oss.qualcomm.com,tushar.nimkar@amd.com,
	akpm@linux-foundation.org
Subject: + mailmap-update-email-address-for-tushar-nimkar.patch added to mm-nonmm-hotfixes-unstable branch
Date: Wed, 18 Nov 2026 22:01:44 -0800	[thread overview]
Message-ID: <20261119060144.D126C1F000C4@smtp.kernel.org> (raw)
In-Reply-To: <20261118-mailmap-update-v1-1-b7197cd9d19e@amd.com>


The patch titled
     Subject: .mailmap: update email address for Tushar Nimkar
has been added to the -mm mm-nonmm-hotfixes-unstable branch.  Its filename is
     mailmap-update-email-address-for-tushar-nimkar.patch

This patch will shortly appear at
     https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mailmap-update-email-address-for-tushar-nimkar.patch

This patch will later appear in the mm-nonmm-hotfixes-unstable branch at
    git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***

The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days

------------------------------------------------------
From: Tushar Nimkar <tushar.nimkar@amd.com>
Subject: .mailmap: update email address for Tushar Nimkar
Date: Wed, 18 Nov 2026 15:43:40 +0530

Map my old Qualcomm email address to my current AMD email address.

Link: https://patch.msgid.link/20261118-mailmap-update-v1-1-b7197cd9d19e@amd.com
Signed-off-by: Tushar Nimkar <tushar.nimkar@amd.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Suggested-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: Michal Simek <michal.simek@amd.com>
Cc: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>

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

--- a/.mailmap~mailmap-update-email-address-for-tushar-nimkar
+++ a/.mailmap
@@ -974,6 +974,7 @@ TripleX Chung <xxx.phy@gmail.com> <tripl
 TripleX Chung <xxx.phy@gmail.com> <zhongyu@18mail.cn>
 Tsuneo Yoshioka <Tsuneo.Yoshioka@f-secure.com>
 Tudor Ambarus <tudor.ambarus@linaro.org> <tudor.ambarus@microchip.com>
+Tushar Nimkar <tushar.nimkar@amd.com> <quic_tnimkar@quicinc.com>
 Tvrtko Ursulin <tursulin@ursulin.net> <tvrtko.ursulin@intel.com>
 Tvrtko Ursulin <tursulin@ursulin.net> <tvrtko.ursulin@linux.intel.com>
 Tvrtko Ursulin <tursulin@ursulin.net> <tvrtko.ursulin@sophos.com>
_

Patches currently in -mm which might be from tushar.nimkar@amd.com are

mailmap-update-email-address-for-tushar-nimkar.patch


           reply	other threads:[~2026-11-19  6:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20261118-mailmap-update-v1-1-b7197cd9d19e@amd.com>]

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=20261119060144.D126C1F000C4@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=michal.simek@amd.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=radhey.shyam.pandey@amd.com \
    --cc=tushar.nimkar@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox