From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: "Joachim Eastwood" <manabian@gmail.com>,
"Pankaj Dubey" <pankaj.dubey@samsung.com>,
dianders@chromium.org, kgene.kim@samsung.com,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"Heiko Stübner" <heiko@sntech.de>,
naushad@samsung.com, Li.Xiubo@freescale.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Tomasz Figa" <tomasz.figa@gmail.com>,
linux-samsung-soc@vger.kernel.org, thomas.ab@samsung.com,
vikas.sajjan@samsung.com, chow.kim@samsung.com,
"Lee Jones" <lee.jones@linaro.org>,
"sunil joshi" <joshi@samsung.com>,
b29396@freescale.com
Subject: Re: [PATCH v5] mfd: syscon: Decouple syscon interface from platform devices
Date: Fri, 26 Sep 2014 09:16:29 +0200 [thread overview]
Message-ID: <2553182.6YgvmDLuEA@wuerfel> (raw)
In-Reply-To: <CAGhQ9VxwTS9=biwp0nCKu2bVU2aNe679aKR=HU5rd_Uaw99sUw@mail.gmail.com>
On Friday 26 September 2014 07:34:12 Joachim Eastwood wrote:
> I am working on Cortex-M4 no-MMU platform that isn't upstream yet, btw.
>
Sorry for drifting off-topic, but this is very interesting to me. Can you
say which one you are working on and what your timeline is for submitting
it upstream?
I generally like to know about new platforms early, and sometimes we get
multiple people working on the same one.
Arnd
next prev parent reply other threads:[~2014-09-26 7:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 4:40 [PATCH v5] mfd: syscon: Decouple syscon interface from platform devices Pankaj Dubey
2014-09-22 9:19 ` Dong Aisheng
2014-09-23 10:29 ` Pankaj Dubey
2014-09-25 12:42 ` Arnd Bergmann
2014-09-26 5:28 ` Pankaj Dubey
2014-09-26 7:14 ` Arnd Bergmann
2014-09-22 9:55 ` Li.Xiubo
2014-09-23 18:12 ` Joachim Eastwood
2014-09-24 18:35 ` Heiko Stübner
2014-09-25 12:21 ` Heiko Stübner
2014-09-26 4:56 ` Pankaj Dubey
2014-09-26 5:34 ` Joachim Eastwood
2014-09-26 7:16 ` Arnd Bergmann [this message]
2014-09-26 7:48 ` Joachim Eastwood
2014-09-26 9:14 ` Arnd Bergmann
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=2553182.6YgvmDLuEA@wuerfel \
--to=arnd@arndb.de \
--cc=Li.Xiubo@freescale.com \
--cc=b29396@freescale.com \
--cc=chow.kim@samsung.com \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=manabian@gmail.com \
--cc=naushad@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=vikas.sajjan@samsung.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).