From: Greg KH <gregkh@linuxfoundation.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] Documentation: embargoed-hardware-issues.rst: Add myself for RISC-V
Date: Wed, 13 Sep 2023 09:19:38 +0200 [thread overview]
Message-ID: <2023091307-narrow-glider-05fa@gregkh> (raw)
In-Reply-To: <20230912180657.31841-1-palmer@rivosinc.com>
On Tue, Sep 12, 2023 at 11:06:56AM -0700, Palmer Dabbelt wrote:
> I'm not sure exactly how RISC-V fits into the story here, but I'm happy
> to voluteer a sort of catch-all for vendors who aren't otherwise
> represented.
>
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
> Documentation/process/embargoed-hardware-issues.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst
> index cb686238f21d..ac7c52f130c9 100644
> --- a/Documentation/process/embargoed-hardware-issues.rst
> +++ b/Documentation/process/embargoed-hardware-issues.rst
> @@ -251,6 +251,7 @@ an involved disclosed party. The current ambassadors list:
> IBM Z Christian Borntraeger <borntraeger@de.ibm.com>
> Intel Tony Luck <tony.luck@intel.com>
> Qualcomm Trilok Soni <tsoni@codeaurora.org>
> + RISC-V Palmer Dabbelt <palmer@dabbelt.com>
> Samsung Javier González <javier.gonz@samsung.com>
>
> Microsoft James Morris <jamorris@linux.microsoft.com>
Thanks for agreeing to do this, hopefully you'll never have to ever get
notified of anything :)
I'll queue this up in my tree now,
greg k-h
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-09-13 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 18:06 [PATCH] Documentation: embargoed-hardware-issues.rst: Add myself for RISC-V Palmer Dabbelt
2023-09-13 7:19 ` Greg KH [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=2023091307-narrow-glider-05fa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.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