From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@arm.linux.org.uk>,
Jason Cooper <jason@lakedaemon.net>,
Gregory Clement <gregory.clement@bootlin.com>,
Leigh Brown <leigh@solinno.co.uk>,
Lu??s Mendes <luis.p.mendes@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 0/2] PCI: fix pci-mvebu after conversion to common bridge emul code
Date: Fri, 22 Feb 2019 13:45:28 +0100 [thread overview]
Message-ID: <20190222134528.138099c1@windsurf> (raw)
In-Reply-To: <20190222110450.GA32670@e107981-ln.cambridge.arm.com>
Hello Lorenzo,
On Fri, 22 Feb 2019 11:05:12 +0000
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
> > Isn't that sufficient ?
>
> Adding a CC: stable won't hurt so that it is certain it will get
> stable kernels attention, that's what I will do.
Ah, yes, indeed. Sorry for forgetting about these, and thanks for
applying with those Cc: stable added!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@arm.linux.org.uk>,
Jason Cooper <jason@lakedaemon.net>,
linux-pci@vger.kernel.org,
Gregory Clement <gregory.clement@bootlin.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Leigh Brown <leigh@solinno.co.uk>,
Lu??s Mendes <luis.p.mendes@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 0/2] PCI: fix pci-mvebu after conversion to common bridge emul code
Date: Fri, 22 Feb 2019 13:45:28 +0100 [thread overview]
Message-ID: <20190222134528.138099c1@windsurf> (raw)
In-Reply-To: <20190222110450.GA32670@e107981-ln.cambridge.arm.com>
Hello Lorenzo,
On Fri, 22 Feb 2019 11:05:12 +0000
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
> > Isn't that sufficient ?
>
> Adding a CC: stable won't hurt so that it is certain it will get
> stable kernels attention, that's what I will do.
Ah, yes, indeed. Sorry for forgetting about these, and thanks for
applying with those Cc: stable added!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-22 12:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 9:48 [PATCH 0/2] PCI: fix pci-mvebu after conversion to common bridge emul code Thomas Petazzoni
2019-02-20 9:48 ` Thomas Petazzoni
2019-02-20 9:48 ` [PATCH 1/2] PCI: pci-bridge-emul: Create per-bridge copy of register behavior Thomas Petazzoni
2019-02-20 9:48 ` Thomas Petazzoni
2019-02-21 23:01 ` Luís Mendes
2019-02-21 23:01 ` Luís Mendes
2019-02-20 9:48 ` [PATCH 2/2] PCI: pci-bridge-emul: Extend pci_bridge_emul_init() with flags Thomas Petazzoni
2019-02-20 9:48 ` Thomas Petazzoni
2019-02-21 23:03 ` Luís Mendes
2019-02-21 23:03 ` Luís Mendes
2019-02-21 23:23 ` [PATCH 0/2] PCI: fix pci-mvebu after conversion to common bridge emul code Bjorn Helgaas
2019-02-21 23:23 ` Bjorn Helgaas
2019-02-22 8:11 ` Leigh Brown
2019-02-22 8:11 ` Leigh Brown
2019-02-22 8:35 ` Thomas Petazzoni
2019-02-22 8:35 ` Thomas Petazzoni
2019-02-22 11:05 ` Lorenzo Pieralisi
2019-02-22 11:05 ` Lorenzo Pieralisi
2019-02-22 12:45 ` Thomas Petazzoni [this message]
2019-02-22 12:45 ` Thomas Petazzoni
2019-02-22 8:06 ` Leigh Brown
2019-02-22 8:06 ` Leigh Brown
2019-02-22 11:22 ` Lorenzo Pieralisi
2019-02-22 11:22 ` Lorenzo Pieralisi
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=20190222134528.138099c1@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=helgaas@kernel.org \
--cc=jason@lakedaemon.net \
--cc=leigh@solinno.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=luis.p.mendes@gmail.com \
--cc=sebastian.hesselbarth@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.