From: Linus Walleij <linus.walleij@linaro.org>
To: tiejunc@vmware.com
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] A Safety-critical Linux system architecture
Date: Thu, 13 Sep 2018 09:57:13 +0200 [thread overview]
Message-ID: <CACRpkdaUxrX2bPo8nCGHeV6uvx6HDbqP+ufssNAxdyJCH735Rw@mail.gmail.com> (raw)
In-Reply-To: <BY1PR0501MB1462CF95EB4423BD59F5D3EBC51A0@BY1PR0501MB1462.namprd05.prod.outlook.com>
On Thu, Sep 13, 2018 at 5:13 AM Tiejun Chen <tiejunc@vmware.com> wrote:
> > On Wed, Sep 12, 2018 at 12:35:07PM +0200, Linus Walleij wrote:
> > > On Wed, Sep 12, 2018 at 3:18 AM Tiejun Chen <tiejunc@vmware.com> wrote:
> > I do not feel Kernel Summit is the right venue for this discussion.
> I cannot understand why we cannot make this over there.
I have to side with Darren on this one, but I will likely not be at KS myself
so take whatever I say with a grain of salt.
I think the LF projects, specifically SIL2LinuxMP etc need to find their
right place to gather people and IMO the Linux Plumbers Conference
or Embedded Linux Conference would be the best place, it just intuitively
fits the type of subject.
But it is not for me to decide.
For the core kernel, I think tooling to the build system and git annotation
of safety reviews are the only things that come to mind, and it doesn't
need much discussion: somone needs to send patches. If they prove
extremely controversial and lead to lots of discussion (etc) THEN we
might want to discuss it at the kernel summit if things grind to a halt.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-09-13 7:57 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 [this message]
2018-09-13 9:50 ` Greg KH
2018-09-16 11:30 ` Tiejun Chen
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=CACRpkdaUxrX2bPo8nCGHeV6uvx6HDbqP+ufssNAxdyJCH735Rw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tiejunc@vmware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).