From: Randy Dunlap <rdunlap@infradead.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: linux-kernel@vger.kernel.org, patches@linaro.org,
linaro-kernel@lists.linaro.org,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Joe Perches <joe@perches.com>,
linux-doc@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] Documentation: devres: Add devm_kmalloc() et al
Date: Sat, 28 Jun 2014 18:31:00 -0700 [thread overview]
Message-ID: <53AF6C54.4010803@infradead.org> (raw)
In-Reply-To: <1403522918-16509-1-git-send-email-daniel.thompson@linaro.org>
[adding Tejun Heo]
patch OK, Tejun? You want to apply it?
On 06/23/14 04:28, Daniel Thompson wrote:
> Commit 64c862a83... added new alloc variants to the devres managed
> API. These should be included in the list of managed API found in
> devres.txt.
>
> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: Grant Likely <grant.likely@linaro.org>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Joe Perches <joe@perches.com>
> Cc: linux-doc@vger.kernel.org
> ---
> Documentation/driver-model/devres.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/driver-model/devres.txt b/Documentation/driver-model/devres.txt
> index 1525e30..91f5633 100644
> --- a/Documentation/driver-model/devres.txt
> +++ b/Documentation/driver-model/devres.txt
> @@ -234,7 +234,10 @@ certainly invest a bit more effort into libata core layer).
> -----------------------------
>
> MEM
> + devm_kmalloc()
> devm_kzalloc()
> + devm_kmalloc_array()
> + devm_kcalloc()
> devm_kfree()
> devm_kmemdup()
> devm_get_free_pages()
>
--
~Randy
next prev parent reply other threads:[~2014-06-29 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 11:28 [PATCH] Documentation: devres: Add devm_kmalloc() et al Daniel Thompson
2014-06-29 1:31 ` Randy Dunlap [this message]
2014-07-01 20:55 ` Tejun Heo
2014-07-03 9:05 ` [RESEND PATCH] " Daniel Thompson
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=53AF6C54.4010803@infradead.org \
--to=rdunlap@infradead.org \
--cc=daniel.thompson@linaro.org \
--cc=grant.likely@linaro.org \
--cc=joe@perches.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=robh+dt@kernel.org \
--cc=tj@kernel.org \
/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