All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Gustavo Padovan <gustavo@padovan.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, "Rob Clark" <robdclark@gmail.com>,
	"Daniel Stone" <daniels@collabora.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Riley Andrews" <riandrews@android.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"Arve Hjønnevåg" <arve@android.com>,
	"Greg Hackmann" <ghackmann@google.com>,
	"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>,
	"John Harrison" <John.C.Harrison@Intel.com>
Subject: Re: [PATCH v4 3/5] staging/android: remove redundant comments on sync_merge_data
Date: Mon, 29 Feb 2016 09:31:18 +0100	[thread overview]
Message-ID: <56D401D6.7030002@linux.intel.com> (raw)
In-Reply-To: <1456511507-2534-3-git-send-email-gustavo@padovan.org>

Op 26-02-16 om 19:31 schreef Gustavo Padovan:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> struct sync_merge_data already have documentation on top of the
> struct definition. No need to duplicate it.
>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> ---
>  drivers/staging/android/uapi/sync.h | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/android/uapi/sync.h b/drivers/staging/android/uapi/sync.h
> index dd0dd84..f0b41ce 100644
> --- a/drivers/staging/android/uapi/sync.h
> +++ b/drivers/staging/android/uapi/sync.h
> @@ -21,9 +21,9 @@
>   * @fence:	returns the fd of the new fence to userspace
>   */
>  struct sync_merge_data {
> -	__s32	fd2; /* fd of second fence */
> -	char	name[32]; /* name of new fence */
> -	__s32	fence; /* fd on newly created fence */
> +	__s32	fd2;
> +	char	name[32];
> +	__s32	fence;
>  };
>  
>  /**
For the first 3 patches:

Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

WARNING: multiple messages have this Message-ID (diff)
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Gustavo Padovan <gustavo@padovan.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	dri-devel@lists.freedesktop.org,
	"Daniel Stone" <daniels@collabora.com>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Riley Andrews" <riandrews@android.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Rob Clark" <robdclark@gmail.com>,
	"Greg Hackmann" <ghackmann@google.com>,
	"John Harrison" <John.C.Harrison@Intel.com>,
	"Gustavo Padovan" <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH v4 3/5] staging/android: remove redundant comments on sync_merge_data
Date: Mon, 29 Feb 2016 09:31:18 +0100	[thread overview]
Message-ID: <56D401D6.7030002@linux.intel.com> (raw)
In-Reply-To: <1456511507-2534-3-git-send-email-gustavo@padovan.org>

Op 26-02-16 om 19:31 schreef Gustavo Padovan:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> struct sync_merge_data already have documentation on top of the
> struct definition. No need to duplicate it.
>
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> ---
>  drivers/staging/android/uapi/sync.h | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/android/uapi/sync.h b/drivers/staging/android/uapi/sync.h
> index dd0dd84..f0b41ce 100644
> --- a/drivers/staging/android/uapi/sync.h
> +++ b/drivers/staging/android/uapi/sync.h
> @@ -21,9 +21,9 @@
>   * @fence:	returns the fd of the new fence to userspace
>   */
>  struct sync_merge_data {
> -	__s32	fd2; /* fd of second fence */
> -	char	name[32]; /* name of new fence */
> -	__s32	fence; /* fd on newly created fence */
> +	__s32	fd2;
> +	char	name[32];
> +	__s32	fence;
>  };
>  
>  /**
For the first 3 patches:

Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

  reply	other threads:[~2016-02-29  8:31 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 18:31 [PATCH v4 1/5] staging/android: add num_fences field to struct sync_file_info Gustavo Padovan
2016-02-26 18:31 ` Gustavo Padovan
2016-02-26 18:31 ` [PATCH v4 2/5] staging/android: rename SYNC_IOC_FENCE_INFO Gustavo Padovan
2016-02-26 18:31   ` Gustavo Padovan
2016-02-26 18:31 ` [PATCH v4 3/5] staging/android: remove redundant comments on sync_merge_data Gustavo Padovan
2016-02-26 18:31   ` Gustavo Padovan
2016-02-29  8:31   ` Maarten Lankhorst [this message]
2016-02-29  8:31     ` Maarten Lankhorst
2016-02-26 18:31 ` [PATCH v4 4/5] staging/android: refactor SYNC_IOC_FILE_INFO Gustavo Padovan
2016-02-26 18:31   ` Gustavo Padovan
2016-02-26 21:00   ` [PATCH] " Gustavo Padovan
2016-02-26 21:00     ` Gustavo Padovan
2016-02-27  2:18     ` Emil Velikov
2016-02-27  2:18       ` Emil Velikov
2016-02-27 15:25       ` Gustavo Padovan
2016-02-27 15:25         ` Gustavo Padovan
2016-02-29  8:34         ` Emil Velikov
2016-02-29  8:34           ` Emil Velikov
2016-02-29  8:26     ` Maarten Lankhorst
2016-02-29  8:26       ` Maarten Lankhorst
2016-02-29 22:08       ` Gustavo Padovan
2016-02-29 22:08         ` Gustavo Padovan
2016-03-01  8:35         ` Maarten Lankhorst
2016-03-01  8:35           ` Maarten Lankhorst
2016-03-01 11:55           ` Gustavo Padovan
2016-03-01  6:55   ` [PATCH v4 4/5] " Dan Carpenter
2016-03-01  6:55     ` Dan Carpenter
2016-02-26 18:31 ` [PATCH v4 5/5] staging/android: add flags member to sync ioctl structs Gustavo Padovan
2016-02-26 18:31   ` Gustavo Padovan
2016-02-27  2:20   ` Emil Velikov
2016-02-27  2:20     ` Emil Velikov
2016-02-27 15:27     ` Gustavo Padovan
2016-02-29  7:59       ` Emil Velikov
2016-02-29  7:59         ` Emil Velikov
2016-02-29  8:30   ` Maarten Lankhorst
2016-02-29  8:30     ` Maarten Lankhorst
2016-03-01  6:36 ` [PATCH v4 1/5] staging/android: add num_fences field to struct sync_file_info Dan Carpenter
2016-03-01  6:36   ` Dan Carpenter
2016-03-01 11:52   ` Gustavo Padovan
2016-03-01 11:52     ` Gustavo Padovan

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=56D401D6.7030002@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=John.C.Harrison@Intel.com \
    --cc=arve@android.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ghackmann@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=gustavo@padovan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riandrews@android.com \
    --cc=robdclark@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.