From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/3] drop legacy booting for omap3517
Date: Fri, 23 Jan 2015 13:46:37 -0800 [thread overview]
Message-ID: <20150123214637.GA20896@quad.lixom.net> (raw)
In-Reply-To: <54be9e8b.6a58460a.68af.6889SMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Jan 20, 2015 at 10:25:38AM -0800, Tony Lindgren wrote:
> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
>
> Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.20/drop-legacy-3517-v2
>
> for you to fetch changes up to 549f95ed20168daa06901054a028e185ebb905ab:
>
> ARM: OMAP3: Add back Kconfig option MACH_OMAP3517EVM for ASoC (2015-01-20 08:49:08 -0800)
>
> ----------------------------------------------------------------
> We have had omap3517 booting in device tree mode for quite some
> time now and we have at least a minimal dts file for the 3517
> based boards. Also almost all the drivers are usable in device
> tree mode. And if there are any drivers not yet supported in device
> tree mode, those can be enabled using pdata quirks.
>
> This leaves omap3430 to omap3730 as the only remaining mach-omap2
> platforms still booting in legacy mode also. For those were are
> printing a warning during the boot to get people to update their
> systems to boot in device tree mode and slowly converting them
> over to device tree based booting.
Merged into next/cleanup. Thanks!
-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 1/3] drop legacy booting for omap3517
Date: Fri, 23 Jan 2015 13:46:37 -0800 [thread overview]
Message-ID: <20150123214637.GA20896@quad.lixom.net> (raw)
In-Reply-To: <54be9e8b.6a58460a.68af.6889SMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Jan 20, 2015 at 10:25:38AM -0800, Tony Lindgren wrote:
> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
>
> Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.20/drop-legacy-3517-v2
>
> for you to fetch changes up to 549f95ed20168daa06901054a028e185ebb905ab:
>
> ARM: OMAP3: Add back Kconfig option MACH_OMAP3517EVM for ASoC (2015-01-20 08:49:08 -0800)
>
> ----------------------------------------------------------------
> We have had omap3517 booting in device tree mode for quite some
> time now and we have at least a minimal dts file for the 3517
> based boards. Also almost all the drivers are usable in device
> tree mode. And if there are any drivers not yet supported in device
> tree mode, those can be enabled using pdata quirks.
>
> This leaves omap3430 to omap3730 as the only remaining mach-omap2
> platforms still booting in legacy mode also. For those were are
> printing a warning during the boot to get people to update their
> systems to boot in device tree mode and slowly converting them
> over to device tree based booting.
Merged into next/cleanup. Thanks!
-Olof
next parent reply other threads:[~2015-01-23 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54be9e8b.6a58460a.68af.6889SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-23 21:46 ` Olof Johansson [this message]
2015-01-23 21:46 ` [GIT PULL 1/3] drop legacy booting for omap3517 Olof Johansson
2015-01-20 18:25 Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2015-01-20 18:25 Tony Lindgren
2015-01-20 18:25 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=20150123214637.GA20896@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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.