From: Luis Chamberlain <mcgrof@kernel.org>
To: Trilok Soni <tsoni@quicinc.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"javier.gonz@samsung.com" <javier.gonz@samsung.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"a.manzanares@samsung.com" <a.manzanares@samsung.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"darren@os.amperecomputing.com" <darren@os.amperecomputing.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"gost.dev@samsung.com" <gost.dev@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Collins <collinsd@codeaurora.org>,
"tkjos@google.com" <tkjos@google.com>,
"Trilok Soni (QUIC)" <quic_tsoni@quicinc.com>
Subject: Re: [RFC] docs: embargoed-hardware-issues: drop stale embargoed HW contact for Qualcomm
Date: Mon, 23 Jan 2023 15:08:57 -0800 [thread overview]
Message-ID: <Y88Tif1aSjcdl20O@bombadil.infradead.org> (raw)
In-Reply-To: <BY5PR02MB675447B5DB615762D339736BB0C89@BY5PR02MB6754.namprd02.prod.outlook.com>
On Mon, Jan 23, 2023 at 11:05:57PM +0000, Trilok Soni wrote:
> On Mon, Jan 23, 2023 at 2:22 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
> >
> > Emails to tsoni@codeaurora.org bounce from different systems I've used
> > and LinkedIn tells me he's now at Linaro since 2019. That's a 4 year
> > gap where embargo stuff goes to /dev/null for Qualcomm if the first
> > bounce happened in 2019, but I have no way of knowing when that
> > account was disactivated for sure.
>
> I can submit a patch to update it to quic_tsoni@quicinc.com . I am still w/ Qualcomm 😊
Great thanks
Luis
prev parent reply other threads:[~2023-01-23 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 22:22 Luis Chamberlain
2023-01-23 22:34 ` Luis Chamberlain
2023-01-23 22:38 ` Nick Desaulniers
2023-01-23 23:05 ` Trilok Soni
2023-01-23 23:08 ` Luis Chamberlain [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=Y88Tif1aSjcdl20O@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=a.manzanares@samsung.com \
--cc=catalin.marinas@arm.com \
--cc=collinsd@codeaurora.org \
--cc=corbet@lwn.net \
--cc=darren@os.amperecomputing.com \
--cc=dave@stgolabs.net \
--cc=gost.dev@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=javier.gonz@samsung.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=quic_tsoni@quicinc.com \
--cc=tkjos@google.com \
--cc=tsoni@quicinc.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
all inboxes | Powered by JetHome®