From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Luís Mendes" <luis.p.mendes@gmail.com>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: Regression with commit PCI: mvebu: Convert to PCI emulated bridge config space
Date: Tue, 12 Feb 2019 14:41:56 +0100 [thread overview]
Message-ID: <20190212144156.655f6824@windsurf> (raw)
In-Reply-To: <CAEzXK1r_Xf=-JSzrP8+0pgeqE+RE0Vx0JAKM0PW7qzc4fgQLNg@mail.gmail.com>
Hello,
On Mon, 4 Feb 2019 11:09:23 +0000
Luís Mendes <luis.p.mendes@gmail.com> wrote:
> Have you been able to find the issue from the logs?
A separate issue was found with the pci-mvebu integration with the new
emulated bridge code, I added you in the thread.
Could you test if:
https://github.com/tpetazzoni/linux/tree/5.0/marvell/pci-mvebu-fix
improves the situation for you ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-12 13:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEzXK1o9L-bVRGBpAo+a_wYqXZh6_zuebF221Bd8=b-DTL1Q9g@mail.gmail.com>
[not found] ` <CAEzXK1po4ik1oHdwVvVMWEqh8KMdAMY7sxv9OR2bYs54qV6EyA@mail.gmail.com>
2018-12-18 13:42 ` Fwd: Regression with commit PCI: mvebu: Convert to PCI emulated bridge config space Luís Mendes
2018-12-18 13:47 ` Thomas Petazzoni
2018-12-18 14:34 ` Thomas Petazzoni
2018-12-18 15:42 ` Luís Mendes
2018-12-18 20:37 ` Thomas Petazzoni
2018-12-18 23:13 ` Luís Mendes
2019-01-08 10:48 ` Thomas Petazzoni
[not found] ` <CAEzXK1oQd1YNZ5pyNXA76h-3CbBRxmTke=Z-SRusyfqL=Wd8eA@mail.gmail.com>
2019-01-09 8:15 ` Thomas Petazzoni
[not found] ` <CAEzXK1oHqOb3pojfX7JqrirxjOFj=UZZfi6tNNO4y6yC3u9LAA@mail.gmail.com>
2019-02-04 11:09 ` Luís Mendes
2019-02-12 13:41 ` Thomas Petazzoni [this message]
2019-02-13 11:34 ` Luís Mendes
2019-02-13 12:33 ` Thomas Petazzoni
2019-02-13 13:24 ` Luís Mendes
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=20190212144156.655f6824@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=luis.p.mendes@gmail.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.