From: Daniel Vetter <daniel@ffwll.ch>
To: "Vetter, Daniel" <daniel.vetter@intel.com>
Cc: "meghana.madhyastha@gmail.com" <meghana.madhyastha@gmail.com>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"julia.lawall@lip6.fr" <julia.lawall@lip6.fr>,
"seanpaul@chromium.org" <seanpaul@chromium.org>,
"outreachy-kernel@googlegroups.com"
<outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH 0/3] GPU: DRM: drm_agpsupport.c: Code cleanup
Date: Wed, 20 Sep 2017 19:48:28 +0200 [thread overview]
Message-ID: <20170920174828.GA25248@dvetter-linux.ger.corp.intel.com> (raw)
In-Reply-To: <1505775934.6581.6.camel@intel.com>
On Mon, Sep 18, 2017 at 11:05:39PM +0000, Vetter, Daniel wrote:
> On Wed, 2017-09-13 at 15:58 +0300, Jani Nikula wrote:
> > On Wed, 13 Sep 2017, Julia Lawall <julia.lawall@lip6.fr> wrote:
> > > 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 ++++++++++++++++++++++--
> > > > ----------------
> >
> > Please try 'git log --oneline -- drivers/gpu/drm/drm_agpsupport.c'
> > and
> > observe the commit subject prefix used. Please try to follow the
> > style
> > in the area you're changing, not some generic rules.
> >
> > > > �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.
> >
> > I'm not generally fond of pure checkpatch fixes, but patch 3 alone I
> > want enough to pick them all up. ;)
> >
> > But please do submit the series to dri-devel@lists.freedesktop.org.
> > As a
> > matter of policy, we don't apply patches not posted to our subsystem
> > mailing list.
>
> Yeah, stuff needs to go through dri-devel when it's a drm patch (or
> anything else in drivers/gpu). That's why we don't recommend it for the
> very first patch (I guess I should update the text a bit, but I'm
> travelling and don't have login creds nearby).
Hm, not all of these landed. Haneen, can you pls resend the remaining
patches with dri-devel (and maintainers, per scripts/get_maintainer.pl) on
cc?
Thanks, Daniel
> -Daniel
>
> > The scripts/get_maintainer.pl script will help you with the lists,
> > but
> > do use discretion. The script is sometimes misguided, adding *way*
> > too
> > many lists and people. Just the main subsystem list and
> > supporters/maintainers are usually enough.
> >
> >
> > Thanks,
> > Jani.
> >
> >
> Intel Semiconductor AG
> Registered No. 020.30.913.786-7
> Registered Office: Badenerstrasse 549, 8048 Zurich, Switzerland
>
> --
> 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/1505775934.6581.6.camel%40intel.com.
> For more options, visit https://groups.google.com/d/optout.
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2017-09-20 17:48 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 ` [Outreachy kernel] [PATCH 0/3] GPU: DRM: drm_agpsupport.c: Code cleanup Julia Lawall
2017-09-13 12:58 ` Jani Nikula
2017-09-18 23:05 ` Vetter, Daniel
2017-09-20 17:48 ` Daniel Vetter [this message]
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=20170920174828.GA25248@dvetter-linux.ger.corp.intel.com \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=julia.lawall@lip6.fr \
--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.