From: Sean Paul <seanpaul@chromium.org>
To: Paul McQuade <paulmcquad@gmail.com>
Cc: daniel.vetter@intel.com, gustavo@padovan.org,
seanpaul@chromium.org, airlied@linux.ie,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] GPU: drm: Fixed Spacing issue
Date: Mon, 19 Mar 2018 09:34:30 -0400 [thread overview]
Message-ID: <20180319133430.GI223881@art_vandelay> (raw)
In-Reply-To: <20180319005225.1545-1-paulmcquad@gmail.com>
On Mon, Mar 19, 2018 at 12:52:22AM +0000, Paul McQuade wrote:
> "foo * bar" should be "foo *bar"
>
> Signed-off-by: Paul McQuade <paulmcquad@gmail.com>
Thank you for your patches. I've squashed them all into one, fixed up the commit
message and applied them to drm-misc-next.
Sean
> ---
> drivers/gpu/drm/drm_bufs.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_bufs.c b/drivers/gpu/drm/drm_bufs.c
> index 1ee84dd802d4..83b3d0801262 100644
> --- a/drivers/gpu/drm/drm_bufs.c
> +++ b/drivers/gpu/drm/drm_bufs.c
> @@ -129,7 +129,7 @@ static int drm_map_handle(struct drm_device *dev, struct drm_hash_item *hash,
> * type. Adds the map to the map list drm_device::maplist. Adds MTRR's where
> * applicable and if supported by the kernel.
> */
> -static int drm_addmap_core(struct drm_device * dev, resource_size_t offset,
> +static int drm_addmap_core(struct drm_device *dev, resource_size_t offset,
> unsigned int size, enum drm_map_type type,
> enum drm_map_flags flags,
> struct drm_map_list ** maplist)
> @@ -361,7 +361,7 @@ static int drm_addmap_core(struct drm_device * dev, resource_size_t offset,
> return 0;
> }
>
> -int drm_legacy_addmap(struct drm_device * dev, resource_size_t offset,
> +int drm_legacy_addmap(struct drm_device *dev, resource_size_t offset,
> unsigned int size, enum drm_map_type type,
> enum drm_map_flags flags, struct drm_local_map **map_ptr)
> {
> @@ -637,8 +637,8 @@ int drm_legacy_rmmap_ioctl(struct drm_device *dev, void *data,
> *
> * Frees any pages and buffers associated with the given entry.
> */
> -static void drm_cleanup_buf_error(struct drm_device * dev,
> - struct drm_buf_entry * entry)
> +static void drm_cleanup_buf_error(struct drm_device *dev,
> + struct drm_buf_entry *entry)
> {
> int i;
>
> --
> 2.16.2
>
--
Sean Paul, Software Engineer, Google / Chromium OS
prev parent reply other threads:[~2018-03-19 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 0:52 Paul McQuade
2018-03-19 0:52 ` [PATCH 2/4] " Paul McQuade
2018-03-19 0:52 ` [PATCH 3/4] " Paul McQuade
2018-03-19 0:52 ` [PATCH 4/4] GPU: drm: Fixed Coding issue Paul McQuade
2018-03-19 13:34 ` Sean Paul [this message]
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=20180319133430.GI223881@art_vandelay \
--to=seanpaul@chromium.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmcquad@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
Powered by JetHome