Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: stable fix for v3.13
Date: Tue, 4 Feb 2014 02:30:39 +0100	[thread overview]
Message-ID: <20140204013039.GA25262@kroah.com> (raw)
In-Reply-To: <20140114154141.GO19878@titan.lakedaemon.net>

On Tue, Jan 14, 2014 at 10:41:41AM -0500, Jason Cooper wrote:
> arm-soc folks,
> 
> Sorry for the lateness in the window on this one.  I'd like to see it
> get into v3.13 if possible, but if it doesn't get there till v3.13.1, I
> understand.
> 
> This fixes a boot hang experienced on some Openblocks AX3-4 boards.
> Once i2c transaction support was added, it was discovered that the A0
> revision of the Armada XP had broken offload support which causes the
> kernel to hang at boot.  The only way to detect this situation is to
> read the PCI config register to get the SoC revision, then disable
> offload if we are on an A0 SoC.
> 
> Unfortunately, this makes for a rather large patch series against
> stable.  Doing the fix in a smaller patch would create a runtime
> dependency between i2c and PCI which we prefer to avoid.
> 
> I'm Cc'ing Greg and linux-stable as a heads-up, and so they can comment
> or ask questions.

It's a big change for stable, but as it's self-contained, and only
touches one platform/driver, I'll take it...

greg k-h

  reply	other threads:[~2014-02-04  1:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 15:41 [GIT PULL] ARM: mvebu: stable fix for v3.13 Jason Cooper
2014-02-04  1:30 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-14 15:44 Jason Cooper
2014-01-14 19:14 ` Kevin Hilman
2014-01-14 19:17   ` Jason Cooper

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=20140204013039.GA25262@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --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