From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Michael Thayer <michael.thayer@oracle.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
Sean Paul <seanpaul@chromium.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 0/3] drm/vboxvideo: Move the vboxvideo driver out of staging
Date: Tue, 5 Mar 2019 08:03:23 +0100 [thread overview]
Message-ID: <20190305070323.GA1538@kroah.com> (raw)
In-Reply-To: <20190304164724.10210-1-hdegoede@redhat.com>
On Mon, Mar 04, 2019 at 05:47:21PM +0100, Hans de Goede wrote:
> Hi All,
>
> This patch-series addresses the 2 TODO / FIXME items recently reported
> by Daniel and after that moves the vboxvideo driver out of staging.
>
> Note this applies on top of drm-misc-next + this patch:
> https://patchwork.kernel.org/patch/10824279/
>
> Currently that patch is not yet in drm-misc, I can push it myself before
> pushing the rest of this series (after review).
>
> Greg, the intent is for this series to be merged upstream through
> drm-misc, may we have your Acked-by for that please?
>
For all 3:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-05 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 16:47 [PATCH 0/3] drm/vboxvideo: Move the vboxvideo driver out of staging Hans de Goede
2019-03-04 16:47 ` [PATCH 1/3] staging/vboxvideo: Drop initial_mode_queried workaround Hans de Goede
2019-03-04 16:47 ` [PATCH 2/3] staging/vboxvideo: Refactor vbox_update_mode_hints Hans de Goede
2019-03-04 16:47 ` [PATCH 3/3] drm/vboxvideo: Move the vboxvideo driver out of staging Hans de Goede
2019-03-05 7:03 ` Greg Kroah-Hartman [this message]
2019-03-11 13:09 ` [PATCH 0/3] " Daniel Vetter
2019-03-11 16:33 ` Hans de Goede
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=20190305070323.GA1538@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=maxime.ripard@bootlin.com \
--cc=michael.thayer@oracle.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.