From: Bjorn Helgaas <helgaas@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Jayachandran Chandrashekaran Nair
<jayachandran.chandrashekaran@broadcom.com>,
Rob Herring <robh@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v1 0/3] PCI: Avoid touching non-compliant BARs
Date: Tue, 8 Mar 2016 12:16:17 -0600 [thread overview]
Message-ID: <20160308181617.GA23484@localhost> (raw)
In-Reply-To: <20160308180520.GN23621@tassilo.jf.intel.com>
On Tue, Mar 08, 2016 at 10:05:20AM -0800, Andi Kleen wrote:
> > I applied the first two patches, with Andi's Tested-by, to
> > pci/resource for v4.6.
> >
> > Per Jayachandran, the Broadcom patch turned out not to be necessary,
> > so I dropped that one.
>
> Thanks. Can the patches please also be marked Cc: stable
> for earlier kernels.
Sure, done. I updated the pci/resource and next branches.
prev parent reply other threads:[~2016-03-08 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 15:58 [PATCH v1 0/3] PCI: Avoid touching non-compliant BARs Bjorn Helgaas
2016-02-26 15:58 ` [PATCH v1 1/3] PCI: Disable IO/MEM decoding for devices with " Bjorn Helgaas
2016-02-26 15:58 ` [PATCH v1 2/3] x86/PCI: Mark Broadwell-EP Home Agent & PCU as having " Bjorn Helgaas
2016-02-26 15:59 ` [PATCH v1 3/3] PCI: Mark Broadcom Vulcan bridges " Bjorn Helgaas
2016-02-26 16:55 ` [PATCH v1 0/3] PCI: Avoid touching " Andi Kleen
2016-03-08 17:50 ` Bjorn Helgaas
2016-03-08 18:05 ` Andi Kleen
2016-03-08 18:16 ` Bjorn Helgaas [this message]
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=20160308181617.GA23484@localhost \
--to=helgaas@kernel.org \
--cc=ak@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=jayachandran.chandrashekaran@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.org \
--cc=x86@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).