linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Vladimir Murzin <Vladimir.Murzin@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"arnd@arndb.de" <arnd@arndb.de>,
	Mark Rutland <Mark.Rutland@arm.com>,
	"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
	"baruch@tkos.co.il" <baruch@tkos.co.il>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>
Subject: Re: [PATCH 0/6] make memtest a generic kernel feature
Date: Tue, 17 Mar 2015 17:31:11 +0000	[thread overview]
Message-ID: <20150317173111.GA8399@arm.com> (raw)
In-Reply-To: <5508625F.6060600@arm.com>

On Tue, Mar 17, 2015 at 05:20:31PM +0000, Vladimir Murzin wrote:
> On 17/03/15 17:18, Will Deacon wrote:
> > On Mon, Mar 09, 2015 at 10:27:04AM +0000, Vladimir Murzin wrote:
> >> Memtest is a simple feature which fills the memory with a given set of
> >> patterns and validates memory contents, if bad memory regions is detected it
> >> reserves them via memblock API. Since memblock API is widely used by other
> >> architectures this feature can be enabled outside of x86 world.
> >>
> >> This patch set promotes memtest to live under generic mm umbrella and enables
> >> memtest feature for arm/arm64.
> >>
> >> It was reported that this patch set was useful for tracking down an issue with
> >> some errant DMA on an arm64 platform.
> >>
> >> Since it touches x86 and mm bits it'd be great to get ACK/NAK for these bits.
> > 
> > Is your intention for akpm to merge this? I don't mind how it goes upstream,
> > but that seems like a sensible route to me.
> > 
> 
> It is already in -mm tree.

Cracking, I missed the memo somehow.

Will

      parent reply	other threads:[~2015-03-17 17:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 10:27 [PATCH 0/6] make memtest a generic kernel feature Vladimir Murzin
2015-03-09 10:27 ` Vladimir Murzin
2015-03-09 10:27 ` [PATCH 1/6] mm: move memtest under /mm Vladimir Murzin
2015-03-09 10:27   ` Vladimir Murzin
2015-03-09 10:27 ` [PATCH 2/6] memtest: use phys_addr_t for physical addresses Vladimir Murzin
2015-03-09 10:27   ` Vladimir Murzin
2015-03-09 10:27 ` [PATCH 3/6] arm64: add support for memtest Vladimir Murzin
2015-03-09 10:27   ` Vladimir Murzin
2015-03-09 10:27 ` [PATCH 4/6] arm: " Vladimir Murzin
2015-03-09 10:27   ` Vladimir Murzin
2015-03-09 10:27 ` [PATCH 5/6] Kconfig: memtest: update number of test patterns up to 17 Vladimir Murzin
2015-03-09 10:27   ` Vladimir Murzin
2015-03-09 10:27 ` [PATCH 6/6] Documentation: update arch list in the 'memtest' entry Vladimir Murzin
2015-03-09 10:27   ` Vladimir Murzin
2015-03-17 17:18 ` [PATCH 0/6] make memtest a generic kernel feature Will Deacon
2015-03-17 17:18   ` Will Deacon
2015-03-17 17:20   ` Vladimir Murzin
2015-03-17 17:20     ` Vladimir Murzin
2015-03-17 17:31     ` Will Deacon [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=20150317173111.GA8399@arm.com \
    --to=will.deacon@arm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=Vladimir.Murzin@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=baruch@tkos.co.il \
    --cc=hpa@zytor.com \
    --cc=lauraa@codeaurora.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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).