From: Linus Walleij <linus.walleij@linaro.org>
To: Alex Levin <levinale@google.com>
Cc: ksummit@lists.linux.dev, Jesse Barnes <jsbarnes@google.com>
Subject: Re: kSummit proposal - The Linux kernel in ChromeOS
Date: Fri, 27 Aug 2021 00:07:56 +0200 [thread overview]
Message-ID: <CACRpkdYaRALXisvqhF8VyK-m0fz9aUFrurH2u5m=9DS4L3FHXg@mail.gmail.com> (raw)
In-Reply-To: <CAEeCyJZas4LCnMWYTo9Wh49N9DoBChzG869x41BpUoZ+1JmCGQ@mail.gmail.com>
On Tue, Aug 24, 2021 at 3:06 AM Alex Levin <levinale@google.com> wrote:
> - Testing the upstream RC on as many platforms as we can as early as we can.
> - Updating the Linux kernel on existing platforms (millions of users at a time).
> - Managing technical “debt” and keeping the ChromeOS kernel as close
> as possible to the upstream kernel.
> - Current pain points in dealing with upstream.
>
> We feel 45-60 minutes would be enough and will allow a discussion.
I think this is really interesting.
Also explain what this stuff is: drivers/platform/chrome/* and why it is
so necessarily different and can't live in existing subsystems?
Also: your experience with using ACPI and when firmware can be
fixed and when it can not, and when/if the kernel has to accommodate
quirks rather than fixing the firmware.
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-08-26 22:08 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 [this message]
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
[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='CACRpkdYaRALXisvqhF8VyK-m0fz9aUFrurH2u5m=9DS4L3FHXg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=jsbarnes@google.com \
--cc=ksummit@lists.linux.dev \
--cc=levinale@google.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).