All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: zhong jiang <zhongjiang@huawei.com>
Cc: shawnguo@kernel.org, airlied@linux.ie,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpu: do not double put device node in zx_drm_probe
Date: Tue, 18 Sep 2018 17:02:44 +0200	[thread overview]
Message-ID: <20180918150244.GA21766@kroah.com> (raw)
In-Reply-To: <5BA112BC.8080108@huawei.com>

On Tue, Sep 18, 2018 at 10:59:08PM +0800, zhong jiang wrote:
> Hi,  Greg
> 
> Can you pick up the patch? 

Nope:
$ ./scripts/get_maintainer.pl --file drivers/gpu/drm/zte/zx_drm_drv.c
Shawn Guo <shawnguo@kernel.org> (maintainer:DRM DRIVERS FOR ZTE ZX)
David Airlie <airlied@linux.ie> (maintainer:DRM DRIVERS)
dri-devel@lists.freedesktop.org (open list:DRM DRIVERS FOR ZTE ZX)
linux-kernel@vger.kernel.org (open list)

why would I take thi when all of those others are the correct
maintainers?

Also, you only posted this 1 day ago.  Please relax and give people time
and a chance to review your patch.  It is not instant.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: zhong jiang <zhongjiang@huawei.com>
Cc: airlied@linux.ie, shawnguo@kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] gpu: do not double put device node in zx_drm_probe
Date: Tue, 18 Sep 2018 17:02:44 +0200	[thread overview]
Message-ID: <20180918150244.GA21766@kroah.com> (raw)
In-Reply-To: <5BA112BC.8080108@huawei.com>

On Tue, Sep 18, 2018 at 10:59:08PM +0800, zhong jiang wrote:
> Hi,  Greg
> 
> Can you pick up the patch? 

Nope:
$ ./scripts/get_maintainer.pl --file drivers/gpu/drm/zte/zx_drm_drv.c
Shawn Guo <shawnguo@kernel.org> (maintainer:DRM DRIVERS FOR ZTE ZX)
David Airlie <airlied@linux.ie> (maintainer:DRM DRIVERS)
dri-devel@lists.freedesktop.org (open list:DRM DRIVERS FOR ZTE ZX)
linux-kernel@vger.kernel.org (open list)

why would I take thi when all of those others are the correct
maintainers?

Also, you only posted this 1 day ago.  Please relax and give people time
and a chance to review your patch.  It is not instant.

thanks,

greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-09-18 15:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17  2:24 [PATCH] gpu: do not double put device node in zx_drm_probe zhong jiang
2018-08-17  2:24 ` zhong jiang
2018-08-23 11:41 ` zhong jiang
2018-08-23 11:41   ` zhong jiang
2018-08-27  7:18 ` Shawn Guo
2018-09-18 15:19   ` Daniel Vetter
2018-09-18 15:19     ` Daniel Vetter
2018-09-19 21:32     ` Shawn Guo
2018-09-06 14:51 ` zhong jiang
2018-09-06 14:51   ` zhong jiang
2018-09-18 14:59 ` zhong jiang
2018-09-18 14:59   ` zhong jiang
2018-09-18 15:02   ` Greg KH [this message]
2018-09-18 15:02     ` Greg KH
2018-09-18 15:18     ` zhong jiang
2018-09-18 15:18       ` zhong jiang
2018-09-18 15:20     ` 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=20180918150244.GA21766@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=zhongjiang@huawei.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.