From: Daniel Vetter <daniel@ffwll.ch>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>, Joe Perches <joe@perches.com>,
Meng Xu <mengxu.gatech@gmail.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Thomas Meyer <thomas@m3y3r.de>,
Mike Frysinger <vapier@chromium.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Hans de Goede <hdegoede@redhat.com>,
Thierry Reding <treding@nvidia.com>,
David Lechner <david@lechnology.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 2/4] vt: Remove vc_panic_force_write
Date: Tue, 11 Sep 2018 14:11:43 +0200 [thread overview]
Message-ID: <20180911121143.GJ19774@phenom.ffwll.local> (raw)
In-Reply-To: <20180822085919.GA32014@kroah.com>
On Wed, Aug 22, 2018 at 10:59:19AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Aug 22, 2018 at 10:54:03AM +0200, Daniel Vetter wrote:
> > It was only used by the panic support in fbcon, which is now gone.
> > Remove this now dead code too.
> >
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: Kees Cook <keescook@chromium.org>
> > Cc: Joe Perches <joe@perches.com>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Meng Xu <mengxu.gatech@gmail.com>
> > Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
> > Cc: Thomas Meyer <thomas@m3y3r.de>
> > Cc: Mike Frysinger <vapier@chromium.org>
> > Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > Cc: Hans de Goede <hdegoede@redhat.com>
> > Cc: Thierry Reding <treding@nvidia.com>
> > Cc: David Lechner <david@lechnology.com>
> > Cc: Philippe Ombredanne <pombredanne@nexb.com>
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Kate Stewart <kstewart@linuxfoundation.org>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > ---
>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Queued for 4.20/5.0 in drm-misc-next together with the other patches in
this series.
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2018-09-11 12:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180822085418epcas5p30ab8aa4b49ba204f4891760af002bce1@epcas5p3.samsung.com>
2018-08-22 8:54 ` [PATCH 1/4] fbdev: Drop FBINFO_CAN_FORCE_OUTPUT flag Daniel Vetter
2018-08-22 8:54 ` Daniel Vetter
2018-08-22 8:54 ` [PATCH 2/4] vt: Remove vc_panic_force_write Daniel Vetter
2018-08-22 8:59 ` Greg Kroah-Hartman
2018-08-22 8:59 ` Greg Kroah-Hartman
2018-09-11 12:11 ` Daniel Vetter [this message]
2018-08-22 8:54 ` [PATCH 3/4] fbdev: Add FBINFO_HIDE_SMEM_START flag Daniel Vetter
2018-08-22 8:54 ` Daniel Vetter
2018-08-22 8:54 ` Daniel Vetter
2018-09-03 16:48 ` Daniel Vetter
2018-09-03 16:48 ` Daniel Vetter
2018-09-03 16:48 ` Daniel Vetter
2018-09-10 12:51 ` Bartlomiej Zolnierkiewicz
2018-09-10 12:51 ` Bartlomiej Zolnierkiewicz
2018-08-22 8:54 ` [PATCH 4/4] drm/fb: Stop leaking physical address Daniel Vetter
2018-08-22 12:57 ` Sean Paul
2018-08-22 12:57 ` Sean Paul
2018-08-22 9:21 ` ✓ Fi.CI.BAT: success for series starting with [1/4] fbdev: Drop FBINFO_CAN_FORCE_OUTPUT flag Patchwork
2018-08-22 10:09 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-10 12:48 ` [PATCH 1/4] " Bartlomiej Zolnierkiewicz
2018-09-10 12:48 ` Bartlomiej Zolnierkiewicz
2018-09-10 12:48 ` Bartlomiej Zolnierkiewicz
2018-09-11 7:42 ` Daniel Vetter
2018-09-11 7:42 ` Daniel Vetter
2018-09-11 7:42 ` Daniel Vetter
2018-09-11 8:47 ` Bartlomiej Zolnierkiewicz
2018-09-11 8:47 ` Bartlomiej Zolnierkiewicz
2018-09-11 8:47 ` Bartlomiej Zolnierkiewicz
2018-09-11 12:12 ` [Intel-gfx] " Daniel Vetter
2018-09-11 12:12 ` Daniel Vetter
2018-09-11 12:12 ` 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=20180911121143.GJ19774@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=david@lechnology.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mengxu.gatech@gmail.com \
--cc=nicolas.pitre@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.de \
--cc=treding@nvidia.com \
--cc=vapier@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.