From: Simon Horman <horms@verge.net.au>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/4] PCI: rcar, rcar-gen2: More Gen2 compatibility strings
Date: Wed, 10 Feb 2016 18:22:29 +0100 [thread overview]
Message-ID: <20160210172229.GC17671@verge.net.au> (raw)
In-Reply-To: <20160205202135.GA9594@localhost>
On Fri, Feb 05, 2016 at 02:21:35PM -0600, Bjorn Helgaas wrote:
> Hi Simon,
>
> On Mon, Jan 18, 2016 at 02:09:41PM +0900, Simon Horman wrote:
> > this short series adds fallback gen2 and SoC-specific r8a7793 compatibility
> > strings to the rcar PCI and rcar-gen2 PCIE drivers. The intention is to
> > provide a complete set of compatibility strings for known Gen2 SoCs.
> >
> > Bjorn, the intention of the revised changelogs for the r8a7793 is to
> > address your concerns regarding providing an explanation of why there are
> > no driver changes. Please consider taking this series through your tree.
> >
> > Key Changes between v2 and v3:
> > * Enhance changelog to describe why documenting the r8a7793 is necessary
> > and sufficient
> > * Added acks.
> >
> > Key Changes between v1 and v2:
> > * Include "rcar-" in generic bindings
> >
> > Simon Horman (4):
> > PCI: rcar-gen2: add gen2 fallback compatibility string
> > PCI: rcar-gen2: add device tree support for r8a7793
> > PCI: rcar: add gen2 fallback compatibility string
> > PCI: rcar: add device tree support for r8a7793
> >
> > Documentation/devicetree/bindings/pci/pci-rcar-gen2.txt | 12 ++++++++++--
> > Documentation/devicetree/bindings/pci/rcar-pci.txt | 14 +++++++++++---
> > drivers/pci/host/pci-rcar-gen2.c | 1 +
> > drivers/pci/host/pcie-rcar.c | 1 +
> > 4 files changed, 23 insertions(+), 5 deletions(-)
>
> Whew, it took a long time to pound that through my thick skull :)
>
> I think patches 1 and 3 are already in v4.5-rc1, and I applied patches 2
> and 4 to my for-linus branch as below. Please double-check and make sure
> for-linus has everything you want. I'll ask Linus to pull that before
> v4.5.
Thanks,
I checked your for-linus branch and everything seems to be in order.
prev parent reply other threads:[~2016-02-10 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 5:09 [PATCH v3 0/4] PCI: rcar, rcar-gen2: More Gen2 compatibility strings Simon Horman
2016-01-18 5:09 ` [PATCH v3 1/4] PCI: rcar-gen2: add gen2 fallback compatibility string Simon Horman
2016-01-18 5:09 ` [PATCH v3 2/4] PCI: rcar-gen2: add device tree support for r8a7793 Simon Horman
2016-01-18 5:09 ` [PATCH v3 3/4] PCI: rcar: add gen2 fallback compatibility string Simon Horman
2016-01-18 5:09 ` [PATCH v3 4/4] PCI: rcar: add device tree support for r8a7793 Simon Horman
2016-02-05 20:21 ` [PATCH v3 0/4] PCI: rcar, rcar-gen2: More Gen2 compatibility strings Bjorn Helgaas
2016-02-10 17:22 ` Simon Horman [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=20160210172229.GC17671@verge.net.au \
--to=horms@verge.net.au \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@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 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).