From: Tejun Heo <tj@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] resource: Add device-managed request/release_resource()
Date: Fri, 1 Aug 2014 09:58:03 -0400 [thread overview]
Message-ID: <20140801135803.GD21624@htj.dyndns.org> (raw)
In-Reply-To: <20140801135540.GA373@ulmo.nvidia.com>
On Fri, Aug 01, 2014 at 03:55:42PM +0200, Thierry Reding wrote:
> On Fri, Aug 01, 2014 at 08:55:22AM -0400, Tejun Heo wrote:
> > On Fri, Aug 01, 2014 at 02:15:10PM +0200, 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.
> > >
> > > Signed-off-by: Thierry Reding <treding@nvidia.com>
> >
> > Acked-by: Tejun Heo <tj@kernel.org>
> >
> > But please also update Documentation/driver-model/devres.txt.
>
> The patch already contains the below hunk. Do you expect anything more
> to be added to that file?
Oops, I missed that. All look fine to me.
Thanks.
--
tejun
next prev parent reply other threads:[~2014-08-01 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 12:15 [PATCH v2 1/2] resource: Add device-managed request/release_resource() Thierry Reding
2014-08-01 12:15 ` [PATCH v2 2/2] PCI: tegra: Implement a proper resource hierarchy Thierry Reding
2014-08-01 12:55 ` [PATCH v2 1/2] resource: Add device-managed request/release_resource() Tejun Heo
2014-08-01 13:55 ` Thierry Reding
2014-08-01 13:58 ` Tejun Heo [this message]
2014-09-04 20:53 ` 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=20140801135803.GD21624@htj.dyndns.org \
--to=tj@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.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 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).