From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, linux@arm.linux.org.uk
Subject: Re: [GIT PULL] omap fixes against v3.18-rc2
Date: Sun, 2 Nov 2014 13:39:46 -0800 [thread overview]
Message-ID: <20141102213946.GA17643@localhost> (raw)
In-Reply-To: <20141030165019.GA31454@atomide.com>
On Thu, Oct 30, 2014 at 09:50:20AM -0700, Tony Lindgren wrote:
> The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:
>
> Linux 3.18-rc2 (2014-10-26 16:48:41 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/fixes-against-v3.18-rc2
>
> for you to fetch changes up to 4b91f7f3c8b20e073b7bfc098625b37f99789508:
>
> ARM: OMAP2+: Warn about deprecated legacy booting mode (2014-10-29 12:19:20 -0700)
Thanks, merged.
>
> ----------------------------------------------------------------
> Few fixes for omaps to enable NAND BCH so devices won't
> produce errors when booted with omap2plus_defconfig, and
> reduce bloat by making IPV6 a loadable module.
>
> Also let's add a warning about legacy boot being deprecated
> for omap3.
>
> We now have things working with device tree, and only omap3 is
> still booting in legacy mode. So hopefully this warning will
> help move the remaining legacy mode users to boot with device
> tree.
Hm, I think I saw Russell commenting recently about migrating back from
DT to legacy boot on a 3430 board.
> As the total reduction of code and static data is somewhere
> around 20000 lines of code once we remove omap3 legacy mode
> booting, we really do want to make omap3 to boot also in
> device tree mode only over the next few merge cycles.
Yep, that'd be nice.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes against v3.18-rc2
Date: Sun, 2 Nov 2014 13:39:46 -0800 [thread overview]
Message-ID: <20141102213946.GA17643@localhost> (raw)
In-Reply-To: <20141030165019.GA31454@atomide.com>
On Thu, Oct 30, 2014 at 09:50:20AM -0700, Tony Lindgren wrote:
> The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:
>
> Linux 3.18-rc2 (2014-10-26 16:48:41 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/fixes-against-v3.18-rc2
>
> for you to fetch changes up to 4b91f7f3c8b20e073b7bfc098625b37f99789508:
>
> ARM: OMAP2+: Warn about deprecated legacy booting mode (2014-10-29 12:19:20 -0700)
Thanks, merged.
>
> ----------------------------------------------------------------
> Few fixes for omaps to enable NAND BCH so devices won't
> produce errors when booted with omap2plus_defconfig, and
> reduce bloat by making IPV6 a loadable module.
>
> Also let's add a warning about legacy boot being deprecated
> for omap3.
>
> We now have things working with device tree, and only omap3 is
> still booting in legacy mode. So hopefully this warning will
> help move the remaining legacy mode users to boot with device
> tree.
Hm, I think I saw Russell commenting recently about migrating back from
DT to legacy boot on a 3430 board.
> As the total reduction of code and static data is somewhere
> around 20000 lines of code once we remove omap3 legacy mode
> booting, we really do want to make omap3 to boot also in
> device tree mode only over the next few merge cycles.
Yep, that'd be nice.
-Olof
next prev parent reply other threads:[~2014-11-02 23:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 16:50 [GIT PULL] omap fixes against v3.18-rc2 Tony Lindgren
2014-10-30 16:50 ` Tony Lindgren
2014-11-02 21:39 ` Olof Johansson [this message]
2014-11-02 21:39 ` Olof Johansson
2014-11-02 23:53 ` Tony Lindgren
2014-11-02 23:53 ` Tony Lindgren
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=20141102213946.GA17643@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.