From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/10] ARM: shmobile: enable CONFIG_DEVTMPFS in defconfig
Date: Fri, 31 Jan 2014 00:13:21 +0000 [thread overview]
Message-ID: <20140131001321.GE14663@verge.net.au> (raw)
In-Reply-To: <87lhxyi90a.wl%kuninori.morimoto.gx@gmail.com>
Thanks.
I have queued up this series, skipping one patch and slightly modifying
two others as noted below. Details are in replies to the specific patches.
On Thu, Jan 30, 2014 at 09:05:10AM +0100, Geert Uytterhoeven wrote:
> On Thu, Jan 30, 2014 at 1:55 AM, Kuninori Morimoto
> <kuninori.morimoto.gx@gmail.com> wrote:
> > These patches enable DEVTMPFS for all Renesas board
> > on defconfig
> >
> > Kuninori Morimoto (10):
> > ARM: shmobile: marzen: enable CONFIG_DEVTMPFS in defconfig
> > ARM: shmobile: mackerel: enable CONFIG_DEVTMPFS in defconfig
> > ARM: shmobile: lager: enable CONFIG_DEVTMPFS in defconfig
I resolved a minor conflict and queued up this lager patch.
> > ARM: shmobile: kzm9g: enable CONFIG_DEVTMPFS in defconfig
> > ARM: shmobile: kzm9d: enable CONFIG_DEVTMPFS in defconfig
> > ARM: shmobile: koelsch: enable CONFIG_DEVTMPFS in defconfig
This koelsch change is the same as one by Geert that I have already queued up,
I have skipped it.
> > ARM: shmobile: genmai: enable CONFIG_DEVTMPFS in defconfig
> > ARM: shmobile: bockw: enable CONFIG_DEVTMPFS in defconfig
I updated the changelog to include the subject of the reverted patch
and queued up this bockw patch.
> > ARM: shmobile: armadillo: enable CONFIG_DEVTMPFS in defconfig
> > ARM: shmobile: ape6evm: enable CONFIG_DEVTMPFS in defconfig
>
> For all above but koelsch, where it's already set:
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
prev parent reply other threads:[~2014-01-31 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 0:55 [PATCH 0/10] ARM: shmobile: enable CONFIG_DEVTMPFS in defconfig Kuninori Morimoto
2014-01-30 8:05 ` Geert Uytterhoeven
2014-01-31 0:13 ` Simon Horman [this message]
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=20140131001321.GE14663@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.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).