Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	"# v4 . 11+" <stable@vger.kernel.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] Revert "drm/i915: Restore lost "Initialized i915" welcome message"
Date: Wed, 17 May 2017 11:12:28 -0300	[thread overview]
Message-ID: <87mvaby3lf.fsf@dilma.collabora.co.uk> (raw)
In-Reply-To: <20170517131557.7836-1-daniel.vetter@ffwll.ch> (Daniel Vetter's message of "Wed, 17 May 2017 15:15:57 +0200")

Daniel Vetter <daniel.vetter@ffwll.ch> writes:

> This reverts commit bc5ca47c0af4f949ba889e666b7da65569e36093.
>
> Gabriel put this back into generic code with
>
> commit 75f6dfe3e652e1adef8cc1b073c89f3e22103a8f
> Author: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
> Date:   Wed Dec 28 12:32:11 2016 -0200
>
>     drm: Deduplicate driver initialization message
>
> but somehow he missed Chris' patch to add the message meanwhile.

Hmmm.  In the commit message, I even mentioned that i915 was an exception because it
used its own registration handle, so I'm pretty sure I didn't miss that
commit.  Not that this is supposed to make it any better... what the
heck happened back then?? :(

This is

Reviewed-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>


-- 
Gabriel Krisman Bertazi

  parent reply	other threads:[~2017-05-17 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 13:15 [PATCH] Revert "drm/i915: Restore lost "Initialized i915" welcome message" Daniel Vetter
2017-05-17 13:22 ` Chris Wilson
2017-05-17 14:12 ` Gabriel Krisman Bertazi [this message]
2017-05-22  8:56   ` 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=87mvaby3lf.fsf@dilma.collabora.co.uk \
    --to=krisman@collabora.co.uk \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=stable@vger.kernel.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