public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, carlos.bilbao@kernel.org
Cc: avadhut.naik@amd.com, akpm@linux-foundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] .mailmap: Update incorrect entry and my email in MAINTAINERS
Date: Wed, 29 Jan 2025 19:18:34 -0600	[thread overview]
Message-ID: <b8cdce66-b110-4db2-b544-7255ccc16ce7@gmail.com> (raw)
In-Reply-To: <87zfj965bh.fsf@trenco.lwn.net>

On 1/29/25 08:52, Jonathan Corbet wrote:

> Carlos Bilbao <carlos.bilbao.osdev@gmail.com> writes:
>
>> Hello,
>>
>> On 1/28/25 16:05, Jonathan Corbet wrote:
>>> carlos.bilbao@kernel.org writes:
>>>
>>>> From: Carlos Bilbao <carlos.bilbao@kernel.org>
>>>>
>>>> Update .mailmap to fix a mapping and my email address in MAINTAINERS.
>>>>
>>>> Signed-off-by: Carlos Bilbao <carlos.bilbao@kernel.org>
>>>> ---
>>>>  .mailmap    |  1 -
>>>>  MAINTAINERS | 10 +++++-----
>>>>  2 files changed, 5 insertions(+), 6 deletions(-)
>>>>
>>>> diff --git a/.mailmap b/.mailmap
>>>> index 83837191affb..0768824e9d19 100644
>>>> --- a/.mailmap
>>>> +++ b/.mailmap
>>>> @@ -139,7 +139,6 @@ Bryan Tan <bryan-bt.tan@broadcom.com> <bryantan@vmware.com>
>>>>  Cai Huoqing <cai.huoqing@linux.dev> <caihuoqing@baidu.com>
>>>>  Can Guo <quic_cang@quicinc.com> <cang@codeaurora.org>
>>>>  Carl Huang <quic_cjhuang@quicinc.com> <cjhuang@codeaurora.org>
>>>> -Carlos Bilbao <carlos.bilbao.osdev@gmail.com> <carlos.bilbao@amd.com>
>>>>  Carlos Bilbao <carlos.bilbao@kernel.org> <carlos.bilbao.osdev@gmail.com>
>>>>  Carlos Bilbao <carlos.bilbao@kernel.org> <carlos.bilbao@amd.com>
>>>>  Carlos Bilbao <carlos.bilbao@kernel.org> <bilbao@vt.edu>
>>> So I am getting confused ... why not just send me a correct patch for
>>> this file rather than expecting me to apply the incorrect one followed
>>> by the fix?
>>
>> Because the incorrect one already made it upstream AFAIU:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250128&id=ed7c0f5395e05057ae6459fdcfe229fb9aaab5b6
> Hmm... it looks like Andrew took it?  It's still in linux-next, though,
> and could be pulled out.  It really seems better to just do it right
> from the outset?


If that's possible, surely. Sending the patch again with the correct
mappings.


>
> jon


Thanks, Carlos


      reply	other threads:[~2025-01-30  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-25 15:47 [PATCH] .mailmap: Update incorrect entry and my email in MAINTAINERS carlos.bilbao
2025-01-25 16:38 ` Matthew Wilcox
2025-01-28 22:05 ` Jonathan Corbet
2025-01-29  1:12   ` Carlos Bilbao
2025-01-29 14:52     ` Jonathan Corbet
2025-01-30  1:18       ` Carlos Bilbao [this message]

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=b8cdce66-b110-4db2-b544-7255ccc16ce7@gmail.com \
    --to=carlos.bilbao.osdev@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avadhut.naik@amd.com \
    --cc=carlos.bilbao@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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