stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hugh Dickins <hughd@google.com>
Cc: mhocko@suse.cz, kernel@kyup.com, torvalds@linux-foundation.org,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "mm, vmscan: Do not wait for page writeback for GFP_NOFS allocations" has been added to the 3.10-stable tree
Date: Fri, 14 Aug 2015 13:36:39 -0700	[thread overview]
Message-ID: <20150814203639.GA18416@kroah.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1508141141100.11268@eggly.anvils>

On Fri, Aug 14, 2015 at 11:47:38AM -0700, Hugh Dickins wrote:
> On Fri, 14 Aug 2015, gregkh@linuxfoundation.org wrote:
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >     mm, vmscan: Do not wait for page writeback for GFP_NOFS allocations
> > 
> > to the 3.10-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:
> >      mm-vmscan-do-not-wait-for-page-writeback-for-gfp_nofs-allocations.patch
> > and it can be found in the queue-3.10 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.
> 
> Here's a further adjusted version with 3.10's comment also updated:

Thanks for this, I've updated the patch in the queue with this one.

greg k-h

      reply	other threads:[~2015-08-14 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 17:33 Patch "mm, vmscan: Do not wait for page writeback for GFP_NOFS allocations" has been added to the 3.10-stable tree gregkh
2015-08-14 18:47 ` Hugh Dickins
2015-08-14 20:36   ` 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=20150814203639.GA18416@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hughd@google.com \
    --cc=kernel@kyup.com \
    --cc=mhocko@suse.cz \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).