linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	Wenrui Li <wenrui.li@rock-chips.com>,
	Brian Norris <briannorris@chromium.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v8 2/3] of/pci: Add helper function to parse max-link-speed from dt
Date: Mon, 24 Oct 2016 19:17:19 -0500	[thread overview]
Message-ID: <CAL_JsqKyGRU3T-gaFwG43zcChHDHUZhsH7Rn5FASrgnc-RBvCw@mail.gmail.com> (raw)
In-Reply-To: <1476755110-22647-2-git-send-email-shawn.lin@rock-chips.com>

On Mon, Oct 17, 2016 at 8:45 PM, Shawn Lin <shawn.lin@rock-chips.com> wrote:
> This new helper function could be used by host drivers to
> get the limitaion of max link speed provided by dt. If the
> property isn't assigned or is invalid, it will return -EINVAL
> to the caller.
>
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>

Acked-by: Rob Herring <robh@kernel.org>

Rob

  reply	other threads:[~2016-10-25  0:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18  1:45 [PATCH v8 1/3] Documentation/devicetree: Add new property to specify the max link speed Shawn Lin
2016-10-18  1:45 ` [PATCH v8 2/3] of/pci: Add helper function to parse max-link-speed from dt Shawn Lin
2016-10-25  0:17   ` Rob Herring [this message]
2016-10-18  1:45 ` [PATCH v8 3/3] PCI: rockchip: Specify the link capability Shawn Lin
2016-10-18 16:41 ` [PATCH v8 1/3] Documentation/devicetree: Add new property to specify the max link speed Rob Herring
2016-11-11 22:24 ` Bjorn Helgaas

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=CAL_JsqKyGRU3T-gaFwG43zcChHDHUZhsH7Rn5FASrgnc-RBvCw@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=briannorris@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=wenrui.li@rock-chips.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).