Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Davidlohr Bueso <dave.bueso@gmail.com>,
	"Theodore Ts'o" <tytso@mit.edu>,
	 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: Tue, 31 Aug 2021 15:21:33 -0400	[thread overview]
Message-ID: <CA+CK2bCq=6vJYeK=DMRUaeOKDBEnrGvKbhHv=zrUDv3wL_CeRw@mail.gmail.com> (raw)
In-Reply-To: <20210830210521.wy5tmivpgy36oxm6@oracle.com>

Sounds good, to me.

On Mon, Aug 30, 2021 at 5:05 PM Daniel Jordan
<daniel.m.jordan@oracle.com> wrote:
>
> On Mon, Aug 30, 2021 at 01:49:43PM -0700, Davidlohr Bueso wrote:
> > This is fine by me, and we had noted that this proposal was not about
> > performance in the conventional way, so being in ksummit track makes
> > sense.
>
> Agreed, fine by me too.

  reply	other threads:[~2021-08-31 19:22 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
     [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 [this message]
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='CA+CK2bCq=6vJYeK=DMRUaeOKDBEnrGvKbhHv=zrUDv3wL_CeRw@mail.gmail.com' \
    --to=pasha.tatashin@soleen.com \
    --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=tytso@mit.edu \
    /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).