From: Stephen Warren <swarren@wwwdotorg.org>
To: Thierry Reding <thierry.reding@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/6] resource: Add device-managed request/release_resource()
Date: Tue, 26 Aug 2014 10:53:35 -0600 [thread overview]
Message-ID: <53FCBB8F.1040401@wwwdotorg.org> (raw)
In-Reply-To: <1409065898-26887-2-git-send-email-thierry.reding@gmail.com>
On 08/26/2014 09:11 AM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Provide device-managed implementations of the request_resource() and
> release_resource() functions. Upon failure to request a resource, the
> new devm_request_resource() function will output an error message for
> consistent error reporting.
The series,
Tested-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2014-08-26 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 15:11 [PATCH v3 0/6] PCI: tegra: Fixes and Tegra124 support Thierry Reding
2014-08-26 15:11 ` [PATCH v3 1/6] resource: Add device-managed request/release_resource() Thierry Reding
2014-08-26 16:53 ` Stephen Warren [this message]
2014-08-26 15:11 ` [PATCH v3 2/6] PCI: tegra: Implement a proper resource hierarchy Thierry Reding
2014-08-26 15:11 ` Thierry Reding
2014-08-26 15:11 ` [PATCH v3 3/6] PCI: tegra: Clear CLKREQ# enable on port disable Thierry Reding
2014-08-26 15:11 ` [PATCH v3 4/6] PCI: tegra: Fix extended configuration space mapping Thierry Reding
2014-08-26 15:11 ` Thierry Reding
2014-08-26 15:11 ` [PATCH v3 5/6] PCI: tegra: Make sure the PCIe PLL is really reset Thierry Reding
2014-08-26 15:11 ` [PATCH v3 6/6] PCI: tegra: Add Tegra124 support Thierry Reding
2014-09-16 23:00 ` [PATCH v3 0/6] PCI: tegra: Fixes and " 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=53FCBB8F.1040401@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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 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.