All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Russell King <linux@arm.linux.org.uk>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH] mm/memblock: Properly handle overlaps and fix error path
Date: Sun, 06 Mar 2011 15:44:06 -0800	[thread overview]
Message-ID: <4D741C46.70702@zytor.com> (raw)
In-Reply-To: <4D741890.7000607@kernel.org>

On 03/06/2011 03:28 PM, Yinghai Lu wrote:
>>  
>> -	rgnbegin = rgnend = 0; /* supress gcc warnings */
>> -From 1f75ea7782bd83f6402964d3b9889ccd69484e02 Mon Sep 17 00:00:00 2001
>> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>> Date: Mon, 7 Mar 2011 10:18:38 +1100
>> Subject: 
> 
> you put two patches in one mail?
> 

And you quoted the entire email, including both patches, in its entirety
to say that?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Russell King <linux@arm.linux.org.uk>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH] mm/memblock: Properly handle overlaps and fix error path
Date: Sun, 06 Mar 2011 15:44:06 -0800	[thread overview]
Message-ID: <4D741C46.70702@zytor.com> (raw)
In-Reply-To: <4D741890.7000607@kernel.org>

On 03/06/2011 03:28 PM, Yinghai Lu wrote:
>>  
>> -	rgnbegin = rgnend = 0; /* supress gcc warnings */
>> -From 1f75ea7782bd83f6402964d3b9889ccd69484e02 Mon Sep 17 00:00:00 2001
>> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>> Date: Mon, 7 Mar 2011 10:18:38 +1100
>> Subject: 
> 
> you put two patches in one mail?
> 

And you quoted the entire email, including both patches, in its entirety
to say that?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-03-06 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06 23:21 [PATCH] mm/memblock: Properly handle overlaps and fix error path Benjamin Herrenschmidt
2011-03-06 23:21 ` Benjamin Herrenschmidt
2011-03-06 23:28 ` Yinghai Lu
2011-03-06 23:28   ` Yinghai Lu
2011-03-06 23:44   ` H. Peter Anvin [this message]
2011-03-06 23:44     ` H. Peter Anvin
2011-03-07  3:01   ` Benjamin Herrenschmidt
2011-03-07  3:01     ` Benjamin Herrenschmidt

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=4D741C46.70702@zytor.com \
    --to=hpa@zytor.com \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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 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.