All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Meghana Madhyastha <meghana.madhyastha@gmail.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	 Jani Nikula <jani.nikula@linux.intel.com>,
	 Sean Paul <seanpaul@chromium.org>,
	outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 0/3] GPU: DRM: drm_agpsupport.c: Code cleanup
Date: Wed, 13 Sep 2017 13:54:22 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1709131352550.26484@hadrien> (raw)
In-Reply-To: <cover.1505296813.git.meghana.madhyastha@gmail.com>



On Wed, 13 Sep 2017, Meghana Madhyastha wrote:

> These patches fix the checkpath warnings and errors
> in drm_agpsupport.c
>
> Meghana Madhyastha (3):
>   GPU: DRM: Moved EXPORT_SYMBOL so that it immediately followed its
>     function
>   GPU: DRM: Replace "foo * bar" with "foo *bar"
>   GPU: DRM: Remove assignment in if condition
>
>  drivers/gpu/drm/drm_agpsupport.c | 41 ++++++++++++++++++++++------------------
>  1 file changed, 23 insertions(+), 18 deletions(-)

Are the DRM people going to pick this up?  Because Greg will not.  If you
do something that is outside staging at a mentor's suggestion it could be
good to make explicit that the mentor will make sure that the patch will
be applied.

thanks,
julia


>
> --
> 2.7.4
>
> --
> 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/cover.1505296813.git.meghana.madhyastha%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>


  parent reply	other threads:[~2017-09-13 11:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 10:18 [PATCH 0/3] GPU: DRM: drm_agpsupport.c: Code cleanup Meghana Madhyastha
2017-09-13 10:21 ` [PATCH 1/3] GPU: DRM: Moved EXPORT_SYMBOL so that it immediately followed its function Meghana Madhyastha
2017-09-13 11:55   ` [Outreachy kernel] " Julia Lawall
2017-09-13 10:22 ` [PATCH 2/3] GPU: DRM: Replace "foo * bar" with "foo *bar" Meghana Madhyastha
2017-09-13 11:59   ` [Outreachy kernel] " Julia Lawall
2017-09-13 10:23 ` [PATCH 3/3] GPU: DRM: Remove assignment in if condition Meghana Madhyastha
2017-09-13 12:02   ` [Outreachy kernel] " Julia Lawall
2017-09-13 11:54 ` Julia Lawall [this message]
2017-09-13 12:58   ` [Outreachy kernel] [PATCH 0/3] GPU: DRM: drm_agpsupport.c: Code cleanup Jani Nikula
2017-09-18 23:05     ` Vetter, Daniel
2017-09-20 17:48       ` Daniel Vetter
2017-09-20 18:13         ` Sean Paul

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.1709131352550.26484@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=daniel.vetter@intel.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=meghana.madhyastha@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=seanpaul@chromium.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 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.