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 10:47:24 -0800 [thread overview]
Message-ID: <CAOesGMg+jW7SN2+E_FYbwi8GdNhc8KrEsahB-Nn+AseO6kLGXA@mail.gmail.com> (raw)
Message-ID: <20181107184724.0zL_eEVbyl7brpYZjVz7VXm6V8gZTqjN8g0ndefR7Wc@z> (raw)
In-Reply-To: <CAOesGMheCcvDQCd+7fyh4yOk4BYDfm2QRqsdawqA_fg8s9YYEQ@mail.gmail.com>
On Wed, Nov 7, 2018 at 9:35 AM Olof Johansson <olof@lixom.net> wrote:
>
> On Wed, Nov 7, 2018 at 9:17 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> >
> > On Tue, Nov 06, 2018 at 02:16:27PM -0800, Olof Johansson wrote:
> > >
> > > Olof Johansson (arm-soc)
> > > Arnd Bergmann (arm-soc)
> > > Kevin Hilman (arm-soc)
> > > Mike Turquette (clk)
> > > Stephen Boyd (clk)
> > > Linus Walleij (pinctrl + more)
> > > Mike Brown (gpio/regmap + more)
> >
> > Could the poeple listed on this list please list potential schedule conflicts?
> >
> > I'm going to assume we should avoid: Andriod uConf, RISC-V uConf,
> > Device Tree uConf. What are other potential conflicts. I'm going to
> > guess this might be "interesting" to schedule. :-)
>
> Yeah, apologies for adding a bunch of cross-coordination this late too.
>
> It's likely going to be conflict-ridden no matter what we do. RISC-V
> and DT are the main conflicts, Android probably has a bit less.
>
> 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).
Ted,
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.
-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 18:47 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 [this message]
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
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=CAOesGMg+jW7SN2+E_FYbwi8GdNhc8KrEsahB-Nn+AseO6kLGXA@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).