[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181108120017.GB6675@sirena.org.uk>
Date: Thu, 8 Nov 2018 12:00:17 +0000
From: Mark Brown <broonie@...nel.org>
To: "Theodore Y. Ts'o" <tytso@....edu>,
Olof Johansson <olof@...om.net>,
ksummit <ksummit-discuss@...ts.linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-riscv@...ts.infradead.org,
linux-clk <linux-clk@...r.kernel.org>,
linux-gpio@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Palmer Dabbelt <palmer@...ive.com>, rmk@...linux.org.uk,
Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
Arnd Bergmann <arnd@...db.de>,
Michael Turquette <mturquette@...libre.com>,
Kevin Hilman <khilman@...nel.org>,
Stephen Boyd <sboyd@...nel.org>
Subject: Re: [TECH TOPIC] SoC maintainer group
On Wed, Nov 07, 2018 at 12:17:23PM -0500, Theodore Y. Ts'o wrote:
> 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. :-)
The clang BoFs, RT and testing would be bad for me. Possibly some other
stuff but I've not seen the schedule yet.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists