From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: hannes@saeurebad.de, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
stable@kernel.org
Subject: Re: [PATCH 00/20] generic show_mem() v5
Date: Wed, 16 Jul 2008 15:06:32 -0700 [thread overview]
Message-ID: <20080716150632.9b7f3555.akpm@linux-foundation.org> (raw)
In-Reply-To: <1216245100.8711.8.camel@nimitz>
On Wed, 16 Jul 2008 14:51:40 -0700
Dave Hansen <dave@linux.vnet.ibm.com> wrote:
> On Tue, 2008-07-15 at 13:22 -0700, Andrew Morton wrote:
> >
> > > The sections are 512MB, and you can see 6 valid ones
> > > followed by two holes, and then two more valid ones.
> > >
> > > Anyway, I believe this patch will fix the oops.
> >
> > This looks like it might be suitable. Can you please test it?
>
> I compiled, tested, and booted on the machine that had this problem. It
> hasn't reappeared.
>
Confused. Did you have your patch applied or not?
I assume you did, in which case can you please send over a final
changelogged, titled and signed-off patch?
prev parent reply other threads:[~2008-07-16 22:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 16:07 [PATCH 00/20] generic show_mem() v5 Johannes Weiner
2008-07-04 16:07 ` [PATCH 01/20] mm: print swapcache page count in show_swap_cache_info() Johannes Weiner
2008-07-04 16:07 ` [PATCH 02/20] lib: generic show_mem() Johannes Weiner
2008-07-05 8:34 ` Heiko Carstens
2008-07-05 11:29 ` Johannes Weiner
2008-07-05 11:54 ` Heiko Carstens
2008-07-04 16:07 ` [PATCH 03/20] alpha: use " Johannes Weiner
2008-07-04 16:07 ` [PATCH 04/20] avr32: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 05/20] blackfin: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 06/20] xtensa: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 07/20] x86: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 08/20] um: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 09/20] sparc64: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 10/20] sh: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 11/20] s390: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 12/20] powerpc: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 13/20] mn10300: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 14/20] h8300: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 15/20] mips: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 16/20] m68knommu: " Johannes Weiner
2008-07-05 8:11 ` Geert Uytterhoeven
2008-07-05 11:30 ` Johannes Weiner
2008-07-05 12:10 ` Johannes Weiner
2008-07-06 3:34 ` Greg Ungerer
2008-07-06 3:34 ` Greg Ungerer
2008-07-04 16:07 ` [PATCH 17/20] m68k: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 18/20] m32r: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 19/20] frv: " Johannes Weiner
2008-07-04 16:07 ` [PATCH 20/20] cris: " Johannes Weiner
2008-07-04 16:07 ` Johannes Weiner
2008-07-15 19:06 ` [PATCH 00/20] generic show_mem() v5 Dave Hansen
2008-07-15 19:06 ` Dave Hansen
2008-07-15 20:22 ` Andrew Morton
2008-07-15 20:22 ` Andrew Morton
2008-07-15 20:33 ` Dave Hansen
2008-07-16 21:51 ` Dave Hansen
2008-07-16 22:06 ` Andrew Morton [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=20080716150632.9b7f3555.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hannes@saeurebad.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
/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).