From: "Theodore Ts'o" <tytso@mit.edu>
To: Alex Levin <levinale@google.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linus Walleij <linus.walleij@linaro.org>,
ksummit@lists.linux.dev, Jesse Barnes <jsbarnes@google.com>
Subject: Re: kSummit proposal - The Linux kernel in ChromeOS
Date: Mon, 30 Aug 2021 11:19:51 -0400 [thread overview]
Message-ID: <YSz3F8Lp3SigHAd4@mit.edu> (raw)
In-Reply-To: <CAEeCyJY8bXNQHL-kSbxrGcVwQ45kTaR9pW4eOm=ZShEwE5hFiQ@mail.gmail.com>
On Thu, Aug 26, 2021 at 06:01:04PM -0700, Alex Levin wrote:
> Thanks for the feedback Linus and Laurent.
>
> We are willing to extend this to 90 minutes and cover the
> opportunities and challenges we have WRT to SoC manufacturers
> upstreaming and how ChromeOS is influencing upstreaming.
>
> I wasn't sure we will be accepted as a ksummit so it seems that the
> track for now is a MC, but that might change.
Kernel Summit sessions are only 45 minutes, but we do have plenty of
time for BOF's.
What MC track were you proposing this for?
- Ted
next prev parent reply other threads:[~2021-08-30 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 1:05 kSummit proposal - The Linux kernel in ChromeOS Alex Levin
2021-08-26 22:07 ` Linus Walleij
2021-08-26 22:27 ` Laurent Pinchart
2021-08-27 1:01 ` Alex Levin
2021-08-27 20:22 ` Linus Walleij
2021-08-30 17:25 ` Jonathan Cameron
2021-08-30 15:19 ` Theodore Ts'o [this message]
2021-08-30 19:33 ` Theodore Ts'o
[not found] ` <CAMJEoco4eHw6A04nBBtnCMOMW7HsE16uKMsNy02hRP1vt1C-AA@mail.gmail.com>
2021-08-30 20:49 ` Davidlohr Bueso
2021-08-30 21:05 ` Daniel Jordan
2021-08-31 19:21 ` Pavel Tatashin
2021-08-27 13:50 ` Serge E. Hallyn
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=YSz3F8Lp3SigHAd4@mit.edu \
--to=tytso@mit.edu \
--cc=jsbarnes@google.com \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=levinale@google.com \
--cc=linus.walleij@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.