devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Simon Horman <horms@verge.net.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-pci@vger.kernel.org, linux-sh@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/4] PCI: rcar, rcar-gen2: More Gen2 compatibility strings
Date: Fri, 11 Dec 2015 08:59:16 -0600	[thread overview]
Message-ID: <20151211145916.GA21907@localhost> (raw)
In-Reply-To: <20151211021434.GH9927@verge.net.au>

On Fri, Dec 11, 2015 at 11:14:34AM +0900, Simon Horman wrote:
> On Wed, Dec 09, 2015 at 12:37:43PM -0600, Bjorn Helgaas wrote:
> > On Thu, Dec 03, 2015 at 07:51:36AM +0900, Simon Horman wrote:
> > > Hi,
> > > 
> > > this short series adds generic 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.
> > > 
> > > Key Changes in 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(-)
> > 
> > I applied these:
> > 
> > >   PCI: rcar-gen2: add gen2 fallback compatibility string
> > >   PCI: rcar: add gen2 fallback compatibility string
> > 
> > to pci/host-rcar for v4.5, thanks!
> > 
> > I haven't applied the R8A7793 binding documentation updates yet, but
> > I'll be happy to do so given a short description of why they're
> > useful (since they don't update a DT or the driver).  Or they could be
> > merged via a DT tree.
> 
> To clarify: you would like a description in the changelog?

Yes, please.  The email discussion so far hasn't contained what I'm
looking for (if it had, I would have just inserted it and been done
with it).

Apparently it has to do with the stable DT rules, which I don't know.
A concrete example would probably help clear it up.

I've applied the parts that touch PCI.  I won't be offended if the
binding documentation patches go as-is via another tree.  It's just
that if *I'm* going to apply them, I'd like to understand better what
the benefit is.

Bjorn

  reply	other threads:[~2015-12-11 14:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 22:51 [PATCH v2 0/4] PCI: rcar, rcar-gen2: More Gen2 compatibility strings Simon Horman
2015-12-02 22:51 ` [PATCH v2 1/4] PCI: rcar-gen2: add gen2 fallback compatibility string Simon Horman
2015-12-04 15:00   ` Rob Herring
2015-12-07 15:40   ` Bjorn Helgaas
     [not found] ` <1449096700-23304-1-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2015-12-02 22:51   ` [PATCH v2 2/4] PCI: rcar-gen2: add device tree support for r8a7793 Simon Horman
2015-12-04 15:01     ` Rob Herring
2015-12-02 22:51 ` [PATCH v2 3/4] PCI: rcar: add gen2 fallback compatibility string Simon Horman
2015-12-04 15:02   ` Rob Herring
2015-12-07 15:41   ` Bjorn Helgaas
2015-12-02 22:51 ` [PATCH v2 4/4] PCI: rcar: add device tree support for r8a7793 Simon Horman
2015-12-04 15:05   ` Rob Herring
2015-12-09 18:37 ` [PATCH v2 0/4] PCI: rcar, rcar-gen2: More Gen2 compatibility strings Bjorn Helgaas
2015-12-11  2:14   ` Simon Horman
2015-12-11 14:59     ` Bjorn Helgaas [this message]
2015-12-11 15:58       ` Geert Uytterhoeven
2016-02-04 22:01         ` Bjorn Helgaas
2016-02-05  7:43           ` Geert Uytterhoeven
2016-02-05 16:10             ` Bjorn Helgaas
2016-02-05 16:26               ` Geert Uytterhoeven

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=20151211145916.GA21907@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-sh@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).