From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: mvebu: fix PCIe/mvebu-soc-id issue
Date: Tue, 13 May 2014 09:22:45 +0200 [thread overview]
Message-ID: <20140513072245.GA29277@1wt.eu> (raw)
In-Reply-To: <1399903900-29977-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Mon, May 12, 2014 at 04:11:38PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> This set of two patches (and more specifically the second patch) fix a
> PCIe detection problem caused by the introduction of the mvebu-soc-id
> and a bad interaction between the clock manipulation done by the
> mvebu-soc-id code and the PCIe driver. The details are all in the
> commit log of the second patch.
>
> This second patch fixes a PCIe detection problem noticed by several
> persons. The first patch is just a related preparation patch.
>
> Both patches are meant for 3.15-rc, and should be backported to 3.14
> as part of the stable process.
Both tested on 3.14.3, they work perfectly as expected on mirabox with
igb, and on XP-GP with igb, r8169 and myri10ge, including a dual-port
one with a PCIe bridge onboard.
If you want you can add :
Tested-by: Willy Tarreau <w@1wt.eu>
Good job!
Willy
next prev parent reply other threads:[~2014-05-13 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 14:11 [PATCH 0/2] ARM: mvebu: fix PCIe/mvebu-soc-id issue Thomas Petazzoni
2014-05-12 14:11 ` [PATCH 1/2] ARM: mvebu: mvebu-soc-id: add missing clk_put() call Thomas Petazzoni
2014-05-12 15:03 ` Gregory CLEMENT
2014-05-12 14:11 ` [PATCH 2/2] ARM: mvebu: mvebu-soc-id: keep clock enabled if PCIe unit is enabled Thomas Petazzoni
2014-05-12 15:18 ` Gregory CLEMENT
2014-05-12 15:30 ` Willy Tarreau
2014-05-12 14:33 ` [PATCH 0/2] ARM: mvebu: fix PCIe/mvebu-soc-id issue Andrew Lunn
2014-05-13 7:22 ` Willy Tarreau [this message]
2014-05-13 15:13 ` Jason Cooper
2014-05-13 15:17 ` Thomas Petazzoni
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=20140513072245.GA29277@1wt.eu \
--to=w@1wt.eu \
--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 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.