public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Laura Abbott <labbott@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	driverdevel <devel@driverdev.osuosl.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"moderated list:DMA BUFFER SHARING FRAMEWORK"
	<linaro-mm-sig@lists.linaro.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] MAINTAINERS: add dri-devel&linaro-mm for Android ION
Date: Wed, 4 Apr 2018 17:42:43 +0200	[thread overview]
Message-ID: <20180404154243.GB31981@kroah.com> (raw)
In-Reply-To: <CAKMK7uGmtoTiYZ0dCjt44E+1HFFCLFdpoVJYS8o2cK6unzAe9w@mail.gmail.com>

On Wed, Apr 04, 2018 at 05:17:08PM +0200, Daniel Vetter wrote:
> On Wed, Apr 4, 2018 at 4:30 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Wed, Apr 04, 2018 at 07:17:39AM -0700, Laura Abbott wrote:
> >> On 04/04/2018 03:30 AM, Daniel Vetter wrote:
> >> > Most of the other cross-driver gfx infrastructure (dma_buf, dma_fence)
> >> > also gets cross posted to all the relevant gfx/memory lists. Doing the
> >> > same for ION means people won't miss relevant patches.
> >> >
> >>
> >> No problem from me, the rate of checkpatch fixups should be
> >> small these days.
> >>
> >> Acked-by: Laura Abbott <labbott@redhat.com>
> >
> > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> Greg, can you pls stuff this into your staging queue? Imo makes most
> sense there.

Ok, but that will have to wait until after 4.17-rc1 is out as my pull
request for 4.17-rc1 is already sent to Linus.

thanks,

greg k-h

      reply	other threads:[~2018-04-04 15:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 10:30 [PATCH] MAINTAINERS: add dri-devel&linaro-mm for Android ION Daniel Vetter
2018-04-04 14:17 ` Laura Abbott
2018-04-04 14:30   ` Greg Kroah-Hartman
2018-04-04 15:17     ` Daniel Vetter
2018-04-04 15:42       ` Greg Kroah-Hartman [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=20180404154243.GB31981@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=labbott@redhat.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sumit.semwal@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox