From: broonie@kernel.org (Mark Brown)
To: linux-riscv@lists.infradead.org
Subject: [TECH TOPIC] SoC maintainer group
Date: Thu, 8 Nov 2018 12:00:17 +0000 [thread overview]
Message-ID: <20181108120017.GB6675@sirena.org.uk> (raw)
In-Reply-To: <20181107171723.GI9919@thunk.org>
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-riscv/attachments/20181108/0bae645f/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
Olof Johansson <olof@lixom.net>,
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>,
rmk@armlinux.org.uk,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Michael Turquette <mturquette@baylibre.com>,
Kevin Hilman <khilman@kernel.org>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [TECH TOPIC] SoC maintainer group
Date: Thu, 8 Nov 2018 12:00:17 +0000 [thread overview]
Message-ID: <20181108120017.GB6675@sirena.org.uk> (raw)
Message-ID: <20181108120017.0m7AYeJn8GoSxbE0wt0_IJ4023jR98Cdc1nghDrd6Lc@z> (raw)
In-Reply-To: <20181107171723.GI9919@thunk.org>
[-- Attachment #1.1: Type: text/plain, Size: 459 bytes --]
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.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
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-08 12:00 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
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 [this message]
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=20181108120017.GB6675@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-riscv@lists.infradead.org \
/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).