The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Bilbao, Carlos" <carlos.bilbao@amd.com>
To: Jonathan Corbet <corbet@lwn.net>,
	elena.reshetova@intel.com, Akira Yokosawa <akiyks@gmail.com>
Cc: bilbao@vt.edu, "Naik, Avadhut" <Avadhut.Naik@amd.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v3] docs/MAINTAINERS: Update my email address
Date: Wed, 24 Apr 2024 14:38:28 -0500	[thread overview]
Message-ID: <ddaf1b59-fd73-4603-b49e-cf21c9971f3f@amd.com> (raw)
In-Reply-To: <87cyqetwhh.fsf@meer.lwn.net>

Hello,

On 4/24/2024 2:02 PM, Jonathan Corbet wrote:
> "Bilbao, Carlos" <carlos.bilbao@amd.com> writes:
> 
>> In the near future, I will not have access to the email address I used as
>> maintainer of a number of things, mostly in the documentation. Update that
>> address to my personal email address (see Link) so I can continue
>> contributing and update .mailmap.
>>
>> Link: https://lore.kernel.org/all/BL1PR12MB58749FF2BFEDB817DE1FE6CBF82A2@BL1PR12MB5874.namprd12.prod.outlook.com/
>> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
>> ---
>>
>> Change since v2:
>> - Fix .mailmap entry from <old-email> <new-email> to <new-email> <old-email>
>>
>> Changes since v1:
>> - Update .mailmap
> 
> I went to apply this, but it doesn't apply to docs-next.  Which tree was
> this patch done against?

I apologize for the inconvenience. Re-sending now after making sure it
applies to the latest docs-next.

> 
> Thanks,
> 
> jon
> 

Thanks,
Carlos

  reply	other threads:[~2024-04-24 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 16:15 [PATCH v3] docs/MAINTAINERS: Update my email address Bilbao, Carlos
2024-04-24 19:02 ` Jonathan Corbet
2024-04-24 19:38   ` Bilbao, Carlos [this message]
2024-04-24 19:59   ` [PATCH v4] " Bilbao, Carlos
2024-04-26 13:43     ` Jonathan Corbet

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=ddaf1b59-fd73-4603-b49e-cf21c9971f3f@amd.com \
    --to=carlos.bilbao@amd.com \
    --cc=Avadhut.Naik@amd.com \
    --cc=akiyks@gmail.com \
    --cc=bilbao@vt.edu \
    --cc=corbet@lwn.net \
    --cc=elena.reshetova@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox