All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: dave.bueso@gmail.com, daniel.m.jordan@oracle.com,
	pasha.tatashin@soleen.com
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	ksummit@lists.linux.dev, Jesse Barnes <jsbarnes@google.com>,
	Alex Levin <levinale@google.com>
Subject: Re: kSummit proposal - The Linux kernel in ChromeOS
Date: Mon, 30 Aug 2021 15:33:29 -0400	[thread overview]
Message-ID: <YS0yiVVa01xbVu7t@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.

I've added the Performance and Scalability MC runners to this thread.

After taking a closer look at the proposal submitted to the
Performance MC:

   https://linuxplumbersconf.org/event/11/abstracts/1042/

... I noted that (a) the proposal wasn't about scalability in the
traditional sense (e.g., how well does the kernel work on CPU's with
192 cores) but rather scalability of the development process, and (b)
the talk was only scheduled for 20 minutes.

So I talked to Alex off-line, and we agreed that best approach was
probably to transfer his session transferred to the kernel summit
track, where he would be able to get a 45 minute slot --- assuming, of
course, that the Performance MC runners would be OK with this change.

If people would like to talk more than what can fit in a 45 minute
slot, there will be BOF session slots on Friday that people can
request for more conversation.  There will also be "hack rooms" that
are available, which will not be live-streamed nor permanently
recorded.

Dave, Daniel, Pasha --- does this seem reasonable to you?

Thanks,

						- Ted

  parent reply	other threads:[~2021-08-30 19:33 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
2021-08-30 19:33       ` Theodore Ts'o [this message]
     [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=YS0yiVVa01xbVu7t@mit.edu \
    --to=tytso@mit.edu \
    --cc=daniel.m.jordan@oracle.com \
    --cc=dave.bueso@gmail.com \
    --cc=jsbarnes@google.com \
    --cc=ksummit@lists.linux.dev \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=levinale@google.com \
    --cc=linus.walleij@linaro.org \
    --cc=pasha.tatashin@soleen.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 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.