All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: ville.syrjala@linux.intel.com, stable@vger.kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "Revert "drm/i915: Don't skip request retirement if the active list is empty"" has been added to the 4.0-stable tree
Date: Wed, 24 Jun 2015 07:57:42 -0700	[thread overview]
Message-ID: <20150624145742.GC25842@kroah.com> (raw)
In-Reply-To: <87d20m25wc.fsf@intel.com>

On Tue, Jun 23, 2015 at 11:19:47AM +0300, Jani Nikula wrote:
> On Tue, 23 Jun 2015, gregkh@linuxfoundation.org wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> >     Revert "drm/i915: Don't skip request retirement if the active list is empty"
> >
> > to the 4.0-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:
> >      revert-drm-i915-don-t-skip-request-retirement-if-the-active-list-is-empty.patch
> > and it can be found in the queue-4.0 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.
> 
> http://mid.gmane.org/87h9py288m.fsf@intel.com

I have no idea what sending this link means here.  Should I not include
this patch?  Should I ignore the email you link to here?

totally confused,

greg k-h

      reply	other threads:[~2015-06-24 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  3:25 Patch "Revert "drm/i915: Don't skip request retirement if the active list is empty"" has been added to the 4.0-stable tree gregkh
2015-06-23  8:19 ` Jani Nikula
2015-06-24 14:57   ` Greg KH [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=20150624145742.GC25842@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jani.nikula@intel.com \
    --cc=stable-commits@vger.kernel.org \
    --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 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.