From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
chris@chris-wilson.co.uk, antti.koskipaa@linux.intel.com,
tvrtko.ursulin@intel.com, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "drm/i915: Exit cherryview_irq_handler() after one pass" has been added to the 4.4-stable tree
Date: Mon, 2 May 2016 20:07:56 +0300 [thread overview]
Message-ID: <20160502170756.GZ4329@intel.com> (raw)
In-Reply-To: <20160502155017.GB15941@kroah.com>
On Mon, May 02, 2016 at 08:50:17AM -0700, Greg KH wrote:
> On Mon, May 02, 2016 at 09:40:58AM +0300, Jani Nikula wrote:
> > On Mon, 02 May 2016, gregkh@linuxfoundation.org wrote:
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > drm/i915: Exit cherryview_irq_handler() after one pass
> > >
> > > to the 4.4-stable tree which can be found at:
> > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > The filename of the patch is:
> > > drm-i915-exit-cherryview_irq_handler-after-one-pass.patch
> > > and it can be found in the queue-4.4 subdirectory.
> > >
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> >
> > As Ville wrote in another mail, "You don't want this patch. It'll break
> > chv irqs unless you take a half a dozen more patches on top."
>
> So it's ok in 4.5-stable?
No. Needs to dropped from all stable trees.
>
> Dropped from 4.4-stable now.
>
> thanks,
>
> greg k-h
--
Ville Syrj�l�
Intel OTC
next prev parent reply other threads:[~2016-05-02 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 22:16 Patch "drm/i915: Exit cherryview_irq_handler() after one pass" has been added to the 4.4-stable tree gregkh
2016-05-02 6:40 ` Jani Nikula
2016-05-02 15:50 ` Greg KH
2016-05-02 17:07 ` Ville Syrjälä [this message]
2016-05-02 17:13 ` Greg KH
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=20160502170756.GZ4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=antti.koskipaa@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@intel.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tvrtko.ursulin@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 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.