From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: Mention which driver is taking over the VGA console
Date: Mon, 30 Oct 2017 14:40:29 +0200 [thread overview]
Message-ID: <1509367229.4757.1.camel@linux.intel.com> (raw)
In-Reply-To: <20171027213354.14453-1-chris@chris-wilson.co.uk>
On Fri, 2017-10-27 at 22:33 +0100, Chris Wilson wrote:
> Currently there is a rather bland,
>
> [ 4.987589] [drm] Replacing VGA console driver
>
> for when we take over the console. Let's put a (device) name on that.
> If we opt for DRM_DEV_INFO we get
>
> [ 5.071879] i915 0000:00:02.0: [drm:i915_kick_out_vgacon] Replacing VGA console driver
>
> which is a little ugly side for a user message. So just use a plain
> dev_info() instead:
>
> [ 4.948501] i915 0000:00:02.0: Replacing VGA console driver
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Makes sense to me.
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-10-30 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 21:33 [PATCH] drm/i915: Mention which driver is taking over the VGA console Chris Wilson
2017-10-27 22:30 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-10-27 23:39 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-30 8:39 ` [PATCH] " Tvrtko Ursulin
2017-10-30 12:40 ` Joonas Lahtinen [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=1509367229.4757.1.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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