From: Olof Johansson <olof@lixom.net>
To: Theodore Tso <tytso@mit.edu>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-riscv@lists.infradead.org,
linux-clk <linux-clk@vger.kernel.org>,
linux-gpio@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Palmer Dabbelt <palmer@sifive.com>,
Russell King <rmk@armlinux.org.uk>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Kevin Hilman <khilman@kernel.org>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [TECH TOPIC] SoC maintainer group
Date: Wed, 7 Nov 2018 12:35:06 -0800 [thread overview]
Message-ID: <CAOesGMhf-RHtjZGZ9D9i=7=C08zmT9=eW5qnYTO6foB=cz06vA@mail.gmail.com> (raw)
Message-ID: <20181107203506.8jVKPfhbWKSNvzFgTuf5YPBCUAR8NWAsOzhyg-OlRis@z> (raw)
In-Reply-To: <20181107203245.GK9919@thunk.org>
On Wed, Nov 7, 2018 at 12:33 PM Theodore Y. Ts'o <tytso@mit.edu> wrote:
>
> On Wed, Nov 07, 2018 at 10:47:24AM -0800, Olof Johansson wrote:
> >
> > Can we have 3pm-3:30pm on Thursday? It seems relatively low on
> > embedded-related conflicts and at 3 people would have time to migrate
> > from Daniel Vetter's gitlab talk if needed.
>
> I'd really like to keep the slots all 45 minutes, aligned with the LPC
> referreed paper track, since that's what most MC runners were also
> strongly encouraged to do. (Although to be fair, it looks like most
> of the MC runners haven't really stuck with that.)
>
> The rooms are all fairly close to one another, and if you want to wait
> a few minutes pack up and move next door or across the hall, that's
> fine. But it's going to be a lot simpler of we tell people that the
> official starting time is 2:45pm.
Thanks, we can definitely work with that and just start a few minutes
late if there's a lot of movement between the rooms.
(Previous email seems to have crossed in compose/flight, happy to move
to the other thread but it seems like we're maybe mostly done?)
-Olof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-07 20:35 UTC|newest]
Thread overview: 26+ 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:16 ` Olof Johansson
2018-11-06 22:22 ` Olof Johansson
2018-11-06 22:22 ` Olof Johansson
2018-11-06 23:32 ` [Ksummit-discuss] " Laurent Pinchart
2018-11-06 23:32 ` Laurent Pinchart
2018-11-07 17:36 ` Olof Johansson
2018-11-07 17:36 ` Olof Johansson
2018-11-07 17:17 ` Theodore Y. Ts'o
2018-11-07 17:17 ` Theodore Y. Ts'o
2018-11-07 17:35 ` Olof Johansson
2018-11-07 17:35 ` Olof Johansson
2018-11-07 18:47 ` Olof Johansson
2018-11-07 18:47 ` Olof Johansson
2018-11-07 20:32 ` Theodore Y. Ts'o
2018-11-07 20:32 ` Theodore Y. Ts'o
2018-11-07 20:35 ` Olof Johansson [this message]
2018-11-07 20:35 ` Olof Johansson
2018-11-07 18:50 ` Theodore Y. Ts'o
2018-11-07 18:50 ` Theodore Y. Ts'o
2018-11-08 12:00 ` Mark Brown
2018-11-08 12:00 ` Mark Brown
2018-11-07 19:44 ` [Ksummit-discuss] " Rob Herring
2018-11-07 19:44 ` Rob Herring
2018-11-07 20:54 ` Olof Johansson
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='CAOesGMhf-RHtjZGZ9D9i=7=C08zmT9=eW5qnYTO6foB=cz06vA@mail.gmail.com' \
--to=olof@lixom.net \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=khilman@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@sifive.com \
--cc=rmk@armlinux.org.uk \
--cc=sboyd@kernel.org \
--cc=tytso@mit.edu \
--cc=will.deacon@arm.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 NNTP newsgroup(s).