From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dove: update dove_defconfig with a few useful options
Date: Tue, 19 Feb 2013 11:43:19 -0500 [thread overview]
Message-ID: <20130219164319.GO23237@titan.lakedaemon.net> (raw)
In-Reply-To: <201302191615.40971.arnd@arndb.de>
On Tue, Feb 19, 2013 at 04:15:40PM +0000, Arnd Bergmann wrote:
> 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?
crap, should I not have pulled it?
thx,
Jason.
next prev parent reply other threads:[~2013-02-19 16:43 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
2013-02-19 16:43 ` Jason Cooper [this message]
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=20130219164319.GO23237@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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