From: Thomas Gleixner <tglx@linutronix.de>
To: Jiri Kosina <jikos@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] DRAFT Maintainer's Summit Agenda and Attendee List
Date: Fri, 6 Sep 2019 08:16:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1909060815210.1902@nanos.tec.linutronix.de> (raw)
In-Reply-To: <nycvar.YFH.7.76.1909052354230.31470@cbobk.fhfr.pm>
On Thu, 5 Sep 2019, Jiri Kosina wrote:
> I'd actually like to propose one more topic; last year, we've been
> discussing the process around handling of HW security issues [1]. There
> have been quite some developments since then (and there are still a few
> unresolved companies^Wissues), and I believe it'd be appropriate to give a
> brief update and discuss next steps.
>
> People necessary to discuss this are already on the attendee list, so all
> is good there.
I'm happy to give a brief report. Shouldn't take long.
Thanks,
tglx
prev parent reply other threads:[~2019-09-06 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 15:47 [Ksummit-discuss] DRAFT Maintainer's Summit Agenda and Attendee List Theodore Y. Ts'o
2019-09-05 15:58 ` Konstantin Ryabitsev
2019-09-05 21:58 ` Jiri Kosina
2019-09-06 6:16 ` Thomas Gleixner [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=alpine.DEB.2.21.1909060815210.1902@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=jikos@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).