From: tytso@mit•edu (Theodore Y. Ts'o)
To: linux-arm-kernel@lists•infradead.org
Subject: [TECH TOPIC] SoC maintainer group
Date: Wed, 7 Nov 2018 13:50:53 -0500 [thread overview]
Message-ID: <20181107185053.GJ9919@thunk.org> (raw)
In-Reply-To: <CAOesGMheCcvDQCd+7fyh4yOk4BYDfm2QRqsdawqA_fg8s9YYEQ@mail.gmail.com>
On Wed, Nov 07, 2018 at 09:35:09AM -0800, Olof Johansson wrote:
>
> Tuesday afternoon looks least conflict-y when I squint at the
> schedule, or Thursday afternoon (but ideally not overlapping with
> Daniel's DRM/gitlab session).
I've posted a draft schedule, so why don't we move the conversation
about scheduling there. I see a number of options that might work:
Tuesday immediately after lunch (2:00pm), or the last session before
the TAB elections (4:45pm), and on Thursday maybe at 2:45pm?
- Ted
next prev parent reply other threads:[~2018-11-07 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 22:16 [TECH TOPIC] SoC maintainer group Olof Johansson
2018-11-06 22:22 ` Olof Johansson
2018-11-06 23:32 ` [Ksummit-discuss] " Laurent Pinchart
2018-11-07 17:36 ` Olof Johansson
2018-11-07 17:17 ` Theodore Y. Ts'o
2018-11-07 17:35 ` Olof Johansson
2018-11-07 18:47 ` Olof Johansson
2018-11-07 20:32 ` Theodore Y. Ts'o
2018-11-07 20:35 ` Olof Johansson
2018-11-07 18:50 ` Theodore Y. Ts'o [this message]
2018-11-08 12:00 ` Mark Brown
2018-11-07 19:44 ` [Ksummit-discuss] " Rob Herring
2018-11-07 20:54 ` Olof Johansson
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=20181107185053.GJ9919@thunk.org \
--to=tytso@mit$(echo .)edu \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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