All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Xiaowei Song <songxiaowei@hisilicon.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Jon Mason <jonmason@broadcom.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	Joao Pinto <Joao.Pinto@synopsys.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Tanmay Inamdar <tinamdar@apm.com>,
	Shawn Lin <shawn.lin@rock-chips.com>,
	Ley Foon Tan <lftan@altera.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] PCI: Move private DT related functions into private header
Date: Mon, 14 May 2018 10:27:24 +0200	[thread overview]
Message-ID: <CACRpkdbLWMe9+6oi2h9Dr=YGrz6YKY=RXmQdM9R23XbXhbfSmA@mail.gmail.com> (raw)
In-Reply-To: <20180511171530.16068-2-robh@kernel.org>

On Fri, May 11, 2018 at 7:15 PM, Rob Herring <robh@kernel.org> wrote:

> The functions in linux/of_pci.h are primarily used by host bridge
> drivers, so they can be private to drivers/pci/.
>
> The remaining functions are still used mostly in host bridge drivers
> that still live in arch specific code. Hopefully someday, those will get
> moved into drivers/pci as well.
>
> Acked-by: Jingoo Han <jingoohan1@gmail.com>
> Signed-off-by: Rob Herring <robh@kernel.org>

Nice patch!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

  reply	other threads:[~2018-05-14  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 17:15 [PATCH v3 1/2] PCI: dwc: move CONFIG_PCI depends to menu Rob Herring
2018-05-11 17:15 ` [PATCH v3 2/2] PCI: Move private DT related functions into private header Rob Herring
2018-05-14  8:27   ` Linus Walleij [this message]
2018-05-14 17:33 ` [PATCH v3 1/2] PCI: dwc: move CONFIG_PCI depends to menu 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='CACRpkdbLWMe9+6oi2h9Dr=YGrz6YKY=RXmQdM9R23XbXhbfSmA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=Joao.Pinto@synopsys.com \
    --cc=bhelgaas@google.com \
    --cc=fengguang.wu@intel.com \
    --cc=jingoohan1@gmail.com \
    --cc=jonmason@broadcom.com \
    --cc=lftan@altera.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=rjui@broadcom.com \
    --cc=robh@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=songxiaowei@hisilicon.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=tinamdar@apm.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.