From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [v3.14-rc3 BUG] 1) panic and 2) SATA not working (Was Re: [PATCH] ATA: SATA_MV: Add missing Kconfig select statememnt)
Date: Mon, 17 Feb 2014 12:13:16 -0300 [thread overview]
Message-ID: <20140217151315.GB2765@localhost> (raw)
In-Reply-To: <20140129182035.GM30842@htj.dyndns.org>
On Wed, Jan 29, 2014 at 01:20:35PM -0500, Tejun Heo wrote:
> On Wed, Jan 22, 2014 at 08:56:33PM +0100, Andrew Lunn wrote:
> > SATA_MV depends on GENERIC_PHY. So if SATA_MV is built in, GENERIC_PHY
> > cannot be modular. Fixes build error found by kbuild test robot.
> >
> > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
>
> Applied to libata/for-3.14-fixes. Thanks.
>
Tejun, Jason:
The lack of this patch in -rc3, just made my Armada XP GP board panic.
The panic is the same as this one (reported on Kirkwood):
http://www.spinics.net/lists/arm-kernel/msg308080.html
Which is fixed in linux-next (and should be in -rc4, right?) by:
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8ad116e649b21a42e3cccfb3c1b8d5ea52ba19e5
The SATA won't get probed unless this commit from linux-next is also applied:
commit 49c8f1ffe26ffddfb7244a24db21c0b4a79e1c52
Author: Andrew Lunn <andrew@lunn.ch>
Date: Wed Jan 22 20:56:33 2014 +0100
ATA: SATA_MV: Add missing Kconfig select statememnt
I guess it felt through someone cracks...
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next parent reply other threads:[~2014-02-17 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52e00d45.5gijwyKGLiVLcCNX%fengguang.wu@intel.com>
[not found] ` <1390420593-27697-1-git-send-email-andrew@lunn.ch>
[not found] ` <20140129182035.GM30842@htj.dyndns.org>
2014-02-17 15:13 ` Ezequiel Garcia [this message]
2014-02-17 15:23 ` [v3.14-rc3 BUG] 1) panic and 2) SATA not working (Was Re: [PATCH] ATA: SATA_MV: Add missing Kconfig select statememnt) Jason Cooper
2014-02-18 22:50 ` Tejun Heo
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=20140217151315.GB2765@localhost \
--to=ezequiel.garcia@free-electrons.com \
--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;
as well as URLs for NNTP newsgroup(s).