From: Julia Lawall <julia.lawall@lip6.fr>
To: Mamta Shukla <mamtashukla555@gmail.com>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
outreachy-kernel@googlegroups.com, daniel.vetter@ffwll.ch,
sean@poorly.run
Subject: Re: [Outreachy kernel] [PATCH DRM] drm: Shift * to be adjacent to pointer name
Date: Tue, 16 Oct 2018 12:30:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1810161228530.3512@hadrien> (raw)
In-Reply-To: <20181015212644.GA28579@armorer>
On Tue, 16 Oct 2018, Mamta Shukla wrote:
> Shift * to be adjacent to pointer name to follow Linux coding style.
> Issue found with checkpatch.pl
> ERROR: "foo * bar" should be "foo *bar"
The patch looks OK, but at this point, you know how to send a patch, so it
would be better to focus on changes that are more complex than whitespace
issues.
julia
>
> Signed-off-by: Mamta Shukla <mamtashukla555@gmail.com>
> ---
> drivers/gpu/drm/drm_memory.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_memory.c b/drivers/gpu/drm/drm_memory.c
> index d69e4fc..40c4349 100644
> --- a/drivers/gpu/drm/drm_memory.c
> +++ b/drivers/gpu/drm/drm_memory.c
> @@ -51,7 +51,7 @@
> #endif
>
> static void *agp_remap(unsigned long offset, unsigned long size,
> - struct drm_device * dev)
> + struct drm_device *dev)
> {
> unsigned long i, num_pages =
> PAGE_ALIGN(size) / PAGE_SIZE;
> @@ -94,26 +94,26 @@ static void *agp_remap(unsigned long offset, unsigned long size,
> }
>
> /** Wrapper around agp_free_memory() */
> -void drm_free_agp(struct agp_memory * handle, int pages)
> +void drm_free_agp(struct agp_memory *handle, int pages)
> {
> agp_free_memory(handle);
> }
>
> /** Wrapper around agp_bind_memory() */
> -int drm_bind_agp(struct agp_memory * handle, unsigned int start)
> +int drm_bind_agp(struct agp_memory *handle, unsigned int start)
> {
> return agp_bind_memory(handle, start);
> }
>
> /** Wrapper around agp_unbind_memory() */
> -int drm_unbind_agp(struct agp_memory * handle)
> +int drm_unbind_agp(struct agp_memory *handle)
> {
> return agp_unbind_memory(handle);
> }
>
> #else /* CONFIG_AGP */
> static inline void *agp_remap(unsigned long offset, unsigned long size,
> - struct drm_device * dev)
> + struct drm_device *dev)
> {
> return NULL;
> }
> --
> 1.9.1
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20181015212644.GA28579%40armorer.
> For more options, visit https://groups.google.com/d/optout.
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-16 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 21:26 [PATCH DRM] drm: Shift * to be adjacent to pointer name Mamta Shukla
2018-10-16 10:30 ` Julia Lawall [this message]
2018-10-16 12:37 ` [Outreachy kernel] " Daniel Vetter
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=alpine.DEB.2.20.1810161228530.3512@hadrien \
--to=julia.lawall@lip6.fr \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=mamtashukla555@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=sean@poorly.run \
/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