From: Bjorn Helgaas <helgaas@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rob Herring <robh@kernel.org>,
linux-pci <linux-pci@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
"# 3.4.x" <stable@vger.kernel.org>,
Robin Leblon <robin.leblon@ncentric.com>,
Olof Johansson <olof@lixom.net>,
Koen Vandeputte <koen.vandeputte@ncentric.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] arm: cns3xxx: fix writing to wrong PCI registers after alignment
Date: Wed, 30 Jan 2019 17:06:04 -0600 [thread overview]
Message-ID: <20190130230604.GM229773@google.com> (raw)
In-Reply-To: <CAK8P3a2ftPvdBnVacbGcxDpCW6CvBj3ZGBXuVQE46JocXewvgQ@mail.gmail.com>
On Wed, Jan 30, 2019 at 11:08:04PM +0100, Arnd Bergmann wrote:
> On Thu, Jan 24, 2019 at 5:29 PM Lorenzo Pieralisi
> <lorenzo.pieralisi@arm.com> wrote:
> > On Thu, Jan 24, 2019 at 04:23:05PM +0100, Koen Vandeputte wrote:
> > > On 24.01.19 12:56, Lorenzo Pieralisi wrote:
> > > >On Mon, Jan 07, 2019 at 02:45:09PM +0100, Koen Vandeputte wrote:
> > > Purely for my information:
> > >
> > > Testing on a lot of devices here shows a huge improvement towards stability.
> > > Is it possible to get it merged sooner?
> > > Does "queued for 5.1" also mean that backporting to stables only will happen
> > > at 5.1_rc1 release?
> >
> > Yes, I will ask Bjorn if we can send them for one of the upcoming -rc*
> > (so effectively you will get them in v5.0 and propagated to stable
> > earlier), I do not think it is that urgent either though, let me handle
> > that.
>
> We can take them through the soc tree if that's easier, but
> going through Bjorn's tree is also fine.
I have the following on my for-linus branch and I'll ask Linus to pull them
this week, so they will appear in v5.0:
b8b592a3a8d1 ARM: cns3xxx: use actual size reads for PCIe
b3a32f359397 ARM: cns3xxx: fix writing to wrong PCI registers after alignment
Neither is currently marked for stable, but I'll add that if you like.
They're already both marked as:
Fixes: 802b7c06adc7 ("ARM: cns3xxx: Convert PCI to use generic config accessors")
which I think appeared in v4.0.
Bjorn
next prev parent reply other threads:[~2019-01-30 23:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 13:45 [PATCH v2 1/2] arm: cns3xxx: fix writing to wrong PCI registers after alignment Koen Vandeputte
2019-01-07 13:45 ` [PATCH v2 2/2] arm: cns3xxx: use actual size reads for PCIe Koen Vandeputte
2019-01-08 6:10 ` Krzysztof Hałasa
2019-01-25 10:55 ` Krzysztof Hałasa
2019-01-24 11:56 ` [PATCH v2 1/2] arm: cns3xxx: fix writing to wrong PCI registers after alignment Lorenzo Pieralisi
2019-01-24 15:23 ` Koen Vandeputte
2019-01-24 16:27 ` Lorenzo Pieralisi
2019-01-30 22:08 ` Arnd Bergmann
2019-01-30 23:06 ` Bjorn Helgaas [this message]
2019-01-31 8:00 ` Arnd Bergmann
2019-01-31 21:16 ` Bjorn Helgaas
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=20190130230604.GM229773@google.com \
--to=helgaas@kernel.org \
--cc=arnd@arndb.de \
--cc=koen.vandeputte@ncentric.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=robin.leblon@ncentric.com \
--cc=stable@vger.kernel.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).