From: "Gomez Iglesias, Antonio" <antonio.gomez.iglesias@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Do we need this list anymore? (was Re: [PATCH] Raffle 0)
Date: Tue, 14 Jul 2020 15:47:32 -0700 [thread overview]
Message-ID: <eea78c00-857e-848b-e390-94d7b44e0c5a@linux.intel.com> (raw)
In-Reply-To: <87o8oiun3b.fsf@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Greg, Thomas,
We agree we can shut down this list and use new ones as required for
individual issues.
For those in this list but not in Keybase: if you are interested in
receiving futurue notifications and other information like presentations
and papers that we share on Keybase, send me your public key (
antonio.gomez.iglesias@linux.intel.com ). I’ll use it to share that
information with you.
Thomas, would you mind sharing with me the scripts that you used to
create this list?
Thanks,
Antonio
On 7/14/2020 08:34, speck for Thomas Gleixner wrote:
> speck for Greg KH <speck@linutronix.de> writes:
>> Ok, that's something new, can we just tear down this list now and if we
>> need new lists, create them as we have documented in:
>> https://www.kernel.org/doc/html/latest/process/embargoed-hardware-issues.html
>>
>> That way, when we create a new list, we know what it is for, there's a
>> set time limit on it, and no one is confused like this patch caused.
>>
>> We are already doing this for other issues happening, why shouldn't we
>> do it for this one as well?
> I'm happy to shut this thing down.
next prev parent reply other threads:[~2020-07-14 22:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5f0cf7c5.1c69fb81.99805.3f5fSMTPIN_ADDED_BROKEN@mx.google.com>
2020-07-14 5:57 ` [MODERATED] Re: [PATCH] Raffle 0 Greg KH
2020-07-14 8:03 ` Andrew Cooper
2020-07-14 8:14 ` Greg KH
2020-07-14 8:20 ` Greg KH
2020-07-14 8:36 ` Andrew Cooper
2020-07-14 8:44 ` Greg KH
2020-07-14 11:00 ` [MODERATED] Do we need this list anymore? (was Re: [PATCH] Raffle 0) Greg KH
2020-07-14 15:34 ` Thomas Gleixner
2020-07-14 22:47 ` Gomez Iglesias, Antonio [this message]
2020-07-15 13:16 ` Thomas Gleixner
2020-07-14 5:58 ` [MODERATED] Re: [PATCH] Raffle 0 Greg KH
2020-07-14 6:01 ` Greg KH
2020-07-14 22:39 ` Pawan Gupta
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=eea78c00-857e-848b-e390-94d7b44e0c5a@linux.intel.com \
--to=antonio.gomez.iglesias@linux.intel.com \
--cc=speck@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).