public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, vgoyal@redhat.com, gregkh@suse.de
Subject: Re: [PATCH 2/2] Use FIRMWARE_MEMMAP on x86/E820
Date: Fri, 27 Jun 2008 13:14:15 +0200	[thread overview]
Message-ID: <20080627131415.4d482af2@halley.suse.de> (raw)
In-Reply-To: <86802c440806261354y673a5521ie615feafae3b2bd8@mail.gmail.com>

* Yinghai Lu [2008-06-26 13:54]:
>
> looks good...
> 
> will produce one patch update early_reserve_e820_mpc_new or
> early_reserve_e820 to update e820_saved too. that contained updated
> mptable for second kernel without acpi support.

You or me? I don't understand ...



Bernhard
-- 
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development

  reply	other threads:[~2008-06-27 11:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 20:19 x86: Add /sys/firmware/memmap Bernhard Walle
2008-06-26 20:19 ` [PATCH 1/2] " Bernhard Walle
2008-06-26 20:45   ` Vivek Goyal
2008-06-26 22:24   ` Greg KH
2008-06-27 11:08     ` Bernhard Walle
2008-06-26 20:19 ` [PATCH 2/2] Use FIRMWARE_MEMMAP on x86/E820 Bernhard Walle
2008-06-26 20:54   ` Yinghai Lu
2008-06-27 11:14     ` Bernhard Walle [this message]
2008-06-27 18:31       ` Yinghai Lu
  -- strict thread matches above, loose matches on Subject: below --
2008-06-27 11:12 x86: Add /sys/firmware/memmap Bernhard Walle
2008-06-27 11:12 ` [PATCH 2/2] Use FIRMWARE_MEMMAP on x86/E820 Bernhard Walle
2008-06-26  8:14 x86: Add /sys/firmware/memmap Bernhard Walle
2008-06-26  8:14 ` [PATCH 2/2] Use FIRMWARE_MEMMAP on x86/E820 Bernhard Walle
2008-06-25 19:57 x86: Add /sys/firmware/memmap Bernhard Walle
2008-06-25 19:57 ` [PATCH 2/2] Use FIRMWARE_MEMMAP on x86/E820 Bernhard Walle

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=20080627131415.4d482af2@halley.suse.de \
    --to=bwalle@suse.de \
    --cc=gregkh@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.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