From: Thierry Reding <thierry.reding@gmail.com>
To: "gioh.kim" <gioh.kim@lge.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
gunho.lee@lge.com
Subject: Re: [PATCH] Documentation/dma-buf-sharing.txt: update API descriptions
Date: Tue, 13 May 2014 10:44:41 +0200 [thread overview]
Message-ID: <20140513084440.GL6754@ulmo> (raw)
In-Reply-To: <1399895292-29520-1-git-send-email-gioh.kim@lge.com>
[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]
On Mon, May 12, 2014 at 08:48:12PM +0900, gioh.kim wrote:
> From: "gioh.kim" <gioh.kim@lge.com>
It might be good to fix your setup to make this be the same as the name
and email used in the Signed-off-by line below.
> update some descriptions for API arguments and descriptions.
Nit: "Update" since it's the beginning of a sentence.
> Signed-off-by: Gioh Kim <gioh.kim@lge.com>
> ---
> Documentation/dma-buf-sharing.txt | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/dma-buf-sharing.txt b/Documentation/dma-buf-sharing.txt
> index 505e711..1ea89b8 100644
> --- a/Documentation/dma-buf-sharing.txt
> +++ b/Documentation/dma-buf-sharing.txt
> @@ -56,7 +56,7 @@ The dma_buf buffer sharing API usage contains the following steps:
> size_t size, int flags,
> const char *exp_name)
>
> - If this succeeds, dma_buf_export allocates a dma_buf structure, and returns a
> + If this succeeds, dma_buf_export_named allocates a dma_buf structure, and returns a
Perhaps reformat this so that the lines don't exceed 80 characters?
> pointer to the same. It also associates an anonymous file with this buffer,
> so it can be exported. On failure to allocate the dma_buf object, it returns
> NULL.
> @@ -66,7 +66,7 @@ The dma_buf buffer sharing API usage contains the following steps:
>
> Exporting modules which do not wish to provide any specific name may use the
> helper define 'dma_buf_export()', with the same arguments as above, but
> - without the last argument; a __FILE__ pre-processor directive will be
> + without the last argument; a KBUILD_MODNAME pre-processor directive will be
> inserted in place of 'exp_name' instead.
This was already fixed in commit 2e33def0339c (dma-buf: update exp_name
when using dma_buf_export()). Perhaps you should rebase this patch on
top of the latest linux-next.
Otherwise looks good.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-13 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 11:48 [PATCH] Documentation/dma-buf-sharing.txt: update API descriptions gioh.kim
2014-05-13 8:44 ` Thierry Reding [this message]
2014-05-13 23:53 ` Gioh Kim
-- strict thread matches above, loose matches on Subject: below --
2014-05-13 23:49 Gioh Kim
2014-05-20 23:20 ` Bjorn Helgaas
2014-05-21 3:43 ` Sumit Semwal
2014-05-21 4:39 ` 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=20140513084440.GL6754@ulmo \
--to=thierry.reding@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gioh.kim@lge.com \
--cc=gunho.lee@lge.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sumit.semwal@linaro.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