From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <corbet@lwn.net>, <carlos.bilbao@amd.com>, <avadhut.naik@amd.com>,
<alexs@kernel.org>, <iyanteng@loongson.cn>,
<2023002089@link.tyut.edu.cn>, <quic_bjorande@quicinc.com>,
<quic_tsoni@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<workflows@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: embargoed-hardware-issues.rst: Fix Trilok's email
Date: Fri, 2 Feb 2024 10:06:20 -0700 [thread overview]
Message-ID: <66c4830d-8756-3ade-c8ec-af2b334b24e3@quicinc.com> (raw)
In-Reply-To: <2024020223-eskimo-armoire-a517@gregkh>
On 2/2/2024 9:48 AM, Greg KH wrote:
> On Fri, Feb 02, 2024 at 09:41:19AM -0700, Jeffrey Hugo wrote:
>> The servers for the @codeaurora domain have long been retired and any
>> messages addressed to @codeaurora will bounce.
>>
>> Trilok has an entry in .mailmap, but the raw documentation files still
>> list an old @codeaurora address. Update the address in the
>> documentation files for anyone reading them.
>>
>> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
>> ---
>> Documentation/process/embargoed-hardware-issues.rst | 2 +-
>> .../translations/sp_SP/process/embargoed-hardware-issues.rst | 2 +-
>> .../translations/zh_CN/process/embargoed-hardware-issues.rst | 2 +-
>> .../translations/zh_TW/process/embargoed-hardware-issues.rst | 2 +-
>> 4 files changed, 4 insertions(+), 4 deletions(-)
>
> I think we need an ack from Trilok for this :)
That is fair. I expect Trilok will see this in the next day or so, and
respond.
-Jeff
next prev parent reply other threads:[~2024-02-02 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 16:41 Jeffrey Hugo
2024-02-02 16:48 ` Greg KH
2024-02-02 17:06 ` Jeffrey Hugo [this message]
2024-02-02 17:06 ` Carlos Bilbao
2024-02-10 0:59 ` Trilok Soni
2024-02-14 22:06 ` 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=66c4830d-8756-3ade-c8ec-af2b334b24e3@quicinc.com \
--to=quic_jhugo@quicinc.com \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=avadhut.naik@amd.com \
--cc=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=iyanteng@loongson.cn \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=workflows@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