linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Xie XiuQi <xiexiuqi@huawei.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Jim Davis <jim.epost@gmail.com>,
	Chen Gong <gong.chen@linux.intel.com>
Subject: Re: linux-next: Tree for May 18 (mm/memory-failure.c)
Date: Thu, 21 May 2015 18:23:14 +1000	[thread overview]
Message-ID: <20150521182314.442e9cf1@canb.auug.org.au> (raw)
In-Reply-To: <20150521101748.2ff2fb9e@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

Hi Andrew,

On Thu, 21 May 2015 10:17:48 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Wed, 20 May 2015 13:03:20 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > I dropped
> > 
> > memory-failure-export-page_type-and-action-result.patch
> > memory-failure-change-type-of-action_results-param-3-to-enum.patch
> > tracing-add-trace-event-for-memory-failure.patch
> 
> OK, I have dropped them from linux-next as well (on the way fixing up
> "mm/memory-failure: split thp earlier in memory error handling" and
> "mm/memory-failure: me_huge_page() does nothing for thp").

Well, I didn't get this (or the other removal) right, so I have gone
back to what I had yesterday.  Sorry about that.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-05-21  8:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  8:52 linux-next: Tree for May 18 Stephen Rothwell
2015-05-18 15:20 ` linux-next: Tree for May 18 (mm/memory-failure.c) Randy Dunlap
2015-05-19  2:49   ` Naoya Horiguchi
2015-05-19  4:40     ` Randy Dunlap
2015-05-19 13:46     ` Steven Rostedt
2015-05-20  5:36       ` Naoya Horiguchi
2015-05-20  6:01         ` [PATCH v2 1/2] ras: hwpoison: fix build failure around trace_memory_failure_event Naoya Horiguchi
2015-05-20  6:03           ` [PATCH 2/2] trace, ras: move ras_event.h under include/trace/events Naoya Horiguchi
2015-05-20  7:16             ` Naoya Horiguchi
2015-05-20  8:15               ` [PATCH v2] " Naoya Horiguchi
2015-05-20  5:41     ` linux-next: Tree for May 18 (mm/memory-failure.c) Xie XiuQi
2015-05-20  6:09       ` Naoya Horiguchi
2015-05-20  6:19         ` Xie XiuQi
2015-05-20 20:03       ` Andrew Morton
2015-05-21  0:17         ` Stephen Rothwell
2015-05-21  8:23           ` Stephen Rothwell [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=20150521182314.442e9cf1@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=gong.chen@linux.intel.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=xiexiuqi@huawei.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).