All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Travis <mike.travis@hpe.com>
Cc: 20180524201711.732785782@stormcage.americas.sgi.com,
	akpm@linux-foundation.org, andrew.banman@hpe.com,
	dan.j.williams@intel.com, dimitri.sivanich@hpe.com,
	jgross@suse.com, kirill.shutemov@linux.intel.com,
	mhocko@suse.com, mingo@kernel.org, peterz@infradead.org,
	russ.anderson@hpe.com, tglx@linutronix.de,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "x86/platform/UV: Use new set memory block size function" has been added to the 4.14-stable tree
Date: Thu, 28 Jun 2018 23:52:33 +0900	[thread overview]
Message-ID: <20180628145233.GA30738@kroah.com> (raw)
In-Reply-To: <8bbcb31a-ab7e-fdaa-3a3f-19e8def71922@hpe.com>

On Thu, Jun 28, 2018 at 07:31:57AM -0700, Mike Travis wrote:
> Until the original patch that adds the set_memory_block_size_order()
> function is added, then the following two patches should also not be
> applied.  In fact I'm surprised it built with that function undefined.

It didn't, I dropped them and you saw the emails about that.

thanks,

greg k-h

      reply	other threads:[~2018-06-28 15:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <153015170913288@kroah.com>
2018-06-28 14:31 ` Patch "x86/platform/UV: Use new set memory block size function" has been added to the 4.14-stable tree Mike Travis
2018-06-28 14:52   ` 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=20180628145233.GA30738@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=20180524201711.732785782@stormcage.americas.sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew.banman@hpe.com \
    --cc=dan.j.williams@intel.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=jgross@suse.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=mhocko@suse.com \
    --cc=mike.travis@hpe.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=russ.anderson@hpe.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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 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.