From: Tiejun Chen <tiejunc@vmware.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] A Safety-critical Linux system architecture
Date: Sun, 16 Sep 2018 11:30:21 +0000 [thread overview]
Message-ID: <BY1PR0501MB1462154020BE9F249685728AC51F0@BY1PR0501MB1462.namprd05.prod.outlook.com> (raw)
In-Reply-To: <20180913095051.GC634@kroah.com>
[snip]
> These are all very generic questions/topics, why not propose a talk for the KS
> track at Plumbers for it? Or many talks as these really are a lot of different,
> individual things.
Greg and Linus,
Thank you for taking your time on this review.
Now I tend to agree that this'd better be proposed as a candidate to tech talk.
Thanks
Tiejun
prev parent reply other threads:[~2018-09-16 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 1:18 [Ksummit-discuss] [TECH TOPIC] A Safety-critical Linux system architecture Tiejun Chen
2018-09-12 10:35 ` Linus Walleij
2018-09-12 16:29 ` Darren Hart
2018-09-13 3:13 ` Tiejun Chen
2018-09-13 7:57 ` Linus Walleij
2018-09-13 9:50 ` Greg KH
2018-09-16 11:30 ` Tiejun Chen [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=BY1PR0501MB1462154020BE9F249685728AC51F0@BY1PR0501MB1462.namprd05.prod.outlook.com \
--to=tiejunc@vmware.com \
--cc=gregkh@linuxfoundation.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).