From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dove: update dove_defconfig with a few useful options
Date: Tue, 19 Feb 2013 16:15:40 +0000 [thread overview]
Message-ID: <201302191615.40971.arnd@arndb.de> (raw)
In-Reply-To: <20130123151530.GU1758@titan.lakedaemon.net>
On Wednesday 23 January 2013, Jason Cooper wrote:
> On Sun, Jan 13, 2013 at 09:54:07AM -0800, Olof Johansson wrote:
> > This refreshes the dove_defconfig, and adds:
> > PRINTK_TIME
> > DEVTMPFS
> > EXT4
> >
> > They're quite useful, and allows booting a cubox ubuntu rootfs on SD card,
> > since that by default uses ext4.
> >
> > The rest of the churn is due to options and defaults moving around, no
> > functional difference.
> >
> > Signed-off-by: Olof Johansson <olof@lixom.net>
> > Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> >
> > ---
> > arch/arm/configs/dove_defconfig | 28 ++++++++--------------------
> > 1 file changed, 8 insertions(+), 20 deletions(-)
>
> Applied to mvebu/boards
Hi Olof,
I've just tried rebuilding the for-next branch, which turned out very
easy this time, but this one patch is what stuck out: apparently
you had already applied it into for-next, but it is not on
any of the other branches. Do you know what is going on here?
Arnd
next prev parent reply other threads:[~2013-02-19 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 17:54 [PATCH] ARM: dove: update dove_defconfig with a few useful options Olof Johansson
2013-01-23 15:15 ` Jason Cooper
2013-02-19 16:15 ` Arnd Bergmann [this message]
2013-02-19 16:43 ` Jason Cooper
2013-02-19 17:12 ` Arnd Bergmann
2013-02-19 17:46 ` 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=201302191615.40971.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@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