All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
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 2/3] omap gpmc changes for v3.19
Date: Thu, 20 Nov 2014 12:02:41 +0100	[thread overview]
Message-ID: <201411201202.41698.arnd@arndb.de> (raw)
In-Reply-To: <pull-1415814409-868361-2>

On Wednesday 12 November 2014, Tony Lindgren wrote:
> GPMC (General Purpose Memory Controller) changes for omaps. These
> changes allow us to drop dependencies to bootloader timings now
> that the known device tree entries have been fixed. So we can now
> require proper timings to be configured and get rid of the legacy
> smsc91x code.
> 
> Note that this branch has a dependency to the related device tree
> branch sent in a separate pull request as timings are now required.

Does this mean you are breaking compatibility with old dtb files?

Can you be more specific which machines are affected?

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] omap gpmc changes for v3.19
Date: Thu, 20 Nov 2014 12:02:41 +0100	[thread overview]
Message-ID: <201411201202.41698.arnd@arndb.de> (raw)
In-Reply-To: <pull-1415814409-868361-2>

On Wednesday 12 November 2014, Tony Lindgren wrote:
> GPMC (General Purpose Memory Controller) changes for omaps. These
> changes allow us to drop dependencies to bootloader timings now
> that the known device tree entries have been fixed. So we can now
> require proper timings to be configured and get rid of the legacy
> smsc91x code.
> 
> Note that this branch has a dependency to the related device tree
> branch sent in a separate pull request as timings are now required.

Does this mean you are breaking compatibility with old dtb files?

Can you be more specific which machines are affected?

	Arnd

  reply	other threads:[~2014-11-20 11:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 18:05 [GIT PULL 1/3] omap device tree changes for v3.19 Tony Lindgren
2014-11-12 18:05 ` [GIT PULL 2/3] omap gpmc " Tony Lindgren
2014-11-12 18:05 ` Tony Lindgren
2014-11-20 11:02   ` Arnd Bergmann [this message]
2014-11-20 11:02     ` Arnd Bergmann
2014-11-20 16:08     ` Tony Lindgren
2014-11-20 16:08       ` Tony Lindgren
2014-11-20 16:25       ` Tony Lindgren
2014-11-20 16:25         ` Tony Lindgren
2014-11-12 18:05 ` Tony Lindgren
2014-11-12 18:05 ` [GIT PULL 3/3] omap clean-up " Tony Lindgren
2014-11-12 18:05 ` Tony Lindgren
2014-11-12 18:05 ` Tony Lindgren
2014-11-20 10:47 ` [GIT PULL 1/3] omap device tree changes " Arnd Bergmann
2014-11-20 10:47   ` Arnd Bergmann

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=201411201202.41698.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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.