From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Imre Deak <imre.deak@intel.com>
Cc: "Shashank Sharma" <shashank.sharma@intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Jani Nikula" <jani.nikula@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/3] drm/i915/gen9+: Enable hotplug detection early
Date: Mon, 20 Mar 2017 11:28:16 +0100 [thread overview]
Message-ID: <20170320102816.GA2810@kroah.com> (raw)
In-Reply-To: <20170320102359.GA29368@ideak-desk.fi.intel.com>
On Mon, Mar 20, 2017 at 12:23:59PM +0200, Imre Deak wrote:
> On Sat, Mar 18, 2017 at 10:49:53PM +0800, Greg Kroah-Hartman wrote:
> > On Fri, Mar 17, 2017 at 04:04:46PM +0200, Imre Deak wrote:
> > > For LSPCON resume time initialization we need to sample the
> > > corresponding pin's HPD level, but this is only available when HPD
> > > detection is enabled. Currently we enable detection only when enabling
> > > HPD interrupts which is too late, so bring the enabling of detection
> > > earlier.
> > >
> > > This is needed by the next patch.
> > >
> > > Cc: Shashank Sharma <shashank.sharma@intel.com>
> > > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > > Cc: Ville Syrj�l� <ville.syrjala@linux.intel.com>
> > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Reviewed-by: Shashank Sharma <shashank.sharma@intel.com>
> > > Link: http://patchwork.freedesktop.org/patch/msgid/1485509961-9010-2-git-send-email-imre.deak@intel.com
> > > (cherry picked from commit 7fff8126d9cc902b2636d05d5d34894a75174993)
> >
> > There is no such commit id in Linus's tree.
> >
> > See, this is the problem I am talking about! You all are pushing around
> > patches with commit ids that mean nothing to me, or anyone else who
> > isn't using your own development tree.
> >
> > Ugh, horrid. Please fix up and provide me the _real_ commit id of this
> > patch in Linus's tree.
>
> I copied this from the original commit in Linus' tree (2a57d9cce1c0),
> but I agree at this point it doesn't make sense to keep that. I will
> resend the patchset with the IDs fixed for this and the next patch.
Please read Documentation/stable_kernel_rules.txt for how to submit a
patch for the stable tree in a form that I can accept.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-20 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 14:04 [PATCH 0/3] drm/i915/lspcon: Fix resume time initialization Imre Deak
2017-03-17 14:04 ` [PATCH 1/3] drm/i915/lspcon: Enable AUX interrupts for " Imre Deak
2017-03-17 14:04 ` [PATCH 2/3] drm/i915/gen9+: Enable hotplug detection early Imre Deak
2017-03-18 14:49 ` Greg Kroah-Hartman
2017-03-20 10:23 ` Imre Deak
2017-03-20 10:28 ` Greg Kroah-Hartman [this message]
2017-03-17 14:04 ` [PATCH 3/3] drm/i915/lspcon: Fix resume time initialization due to unasserted HPD Imre Deak
2017-03-18 14:50 ` Greg Kroah-Hartman
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=20170320102816.GA2810@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=imre.deak@intel.com \
--cc=jani.nikula@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=shashank.sharma@intel.com \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).