public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Myaskouvskey, Artiom" <artiom.myaskouvskey@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19-rc6-git2] EFI: mapping memory region of runtime services when using memmap kernel parameter
Date: Tue, 21 Nov 2006 08:22:12 -0800	[thread overview]
Message-ID: <456327B4.6000904@oracle.com> (raw)
In-Reply-To: <C1467C8B168BCF40ACEC2324C1A2B074A6A6A5@hasmsx411.ger.corp.intel.com>

Myaskouvskey, Artiom wrote:
> From: Artiom Myaskouvskey <artiom.myaskouvskey@intel.com>
> 
> When using memmap kernel parameter in EFI boot we should also add to memory map 
> memory regions of runtime services to enable their mapping later.
> 
> Signed-off-by: Artiom Myaskouvskey <artiom.myaskouvskey@intel.com>
> ---

Thanks, I can actually apply the patch now, as opposed to the apparently
base64-encoded version that was just junk to me.

Of course, we can't review it easily when it's an attachment.
It would be a Good Thing for you to experiment with some email clients
that can send patches inline (not as attachments, not as base64) and
which do not mangle the whitespace and do not encode the text.

Back to the patch:  it's only for i386.  Does x86_64 need
similar treatment?

-- 
~Randy

  reply	other threads:[~2006-11-21 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21  9:09 [PATCH 2.6.19-rc6-git2] EFI: mapping memory region of runtime services when using memmap kernel parameter Myaskouvskey, Artiom
2006-11-21 16:22 ` Randy Dunlap [this message]
     [not found] <C1467C8B168BCF40ACEC2324C1A2B074A6A6A1@hasmsx411.ger.corp.intel.com>
2006-11-19 18:32 ` Randy Dunlap

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=456327B4.6000904@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=artiom.myaskouvskey@intel.com \
    --cc=linux-kernel@vger.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