From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by galois.linutronix.de (Postfix) with ESMTPS id 276F4404ED for ; Wed, 15 Jul 2020 00:47:36 +0200 (CEST) Subject: [MODERATED] Re: Do we need this list anymore? (was Re: [PATCH] Raffle 0) References: <5f0cf7c5.1c69fb81.99805.3f5fSMTPIN_ADDED_BROKEN@mx.google.com> <20200714055735.GB655193@kroah.com> <676ec4fc-b0df-91a6-92af-46c6c51663ed@citrix.com> <20200714110011.GA1300507@kroah.com> <87o8oiun3b.fsf@nanos.tec.linutronix.de> From: "Gomez Iglesias, Antonio" Message-ID: Date: Tue, 14 Jul 2020 15:47:32 -0700 MIME-Version: 1.0 In-Reply-To: <87o8oiun3b.fsf@nanos.tec.linutronix.de> Content-Type: multipart/mixed; boundary="bpDIGRENgjDSSwfPaCvQyTlkaNNbicSl5" To: speck@linutronix.de List-ID: This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156) --bpDIGRENgjDSSwfPaCvQyTlkaNNbicSl5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-GB Greg, Thomas, =C2=A0 We agree we can shut down this list and use new ones as required for individual issues. =C2=A0 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=E2=80=99ll use it to share th= at information with you. =C2=A0 Thomas, would you mind sharing with me the scripts that you used to create this list? =C2=A0 Thanks, Antonio On 7/14/2020 08:34, speck for Thomas Gleixner wrote: > speck for Greg KH writes: >> Ok, that's something new, can we just tear down this list now and if w= e >> need new lists, create them as we have documented in: >> https://www.kernel.org/doc/html/latest/process/embargoed-hardware-iss= ues.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. --bpDIGRENgjDSSwfPaCvQyTlkaNNbicSl5--