mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>,
	"David Witbrodt" <dawitbro@sbcglobal.net>,
	"Jordan Crouse" <jordan.crouse@amd.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Ivan Kokshaysky" <ink@jurassic.park.msu.ru>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Jesse Barnes" <jbarnes@virtuousgeek.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: split e820 reserved entries record to late v4 - fix v7
Date: Fri, 5 Sep 2008 01:52:49 -0700	[thread overview]
Message-ID: <86802c440809050152p734f54bex60ae512361d79f93@mail.gmail.com> (raw)
In-Reply-To: <20080904190457.GB24990@elte.hu>

On Thu, Sep 4, 2008 at 12:04 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
>> v7: remove wrong removing of write_unlock(&resource_lock) in adjust_resource()
>
> i've applied the generic commit below to tip/core/resources, and merged
> tip/core/resources into tip/x86/core, and added the remaining e820.c
> oneliner change (attached below as well).
>

wonder if need to put

  x86: split e820 reserved entries record to late v4
  IO resources: add reserve_region_with_split()
  x86: split e820 reserved entries record to late, v7

into 2.6.27 for fix hang on David's system.

YH

  parent reply	other threads:[~2008-09-05  8:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01  7:31 Yinghai Lu
2008-09-04 19:04 ` Ingo Molnar
2008-09-04 19:16   ` Andrew Morton
2008-09-04 19:22     ` Yinghai Lu
2008-10-13 20:32       ` Tony Luck
2008-10-13 21:14         ` H. Peter Anvin
2008-10-13 21:17           ` Luck, Tony
2008-10-13 21:46           ` Linus Torvalds
2008-10-13 21:54             ` H. Peter Anvin
2008-10-13 22:40             ` Yinghai Lu
2008-10-13 22:48               ` H. Peter Anvin
2008-10-14  5:29         ` Yinghai Lu
2008-09-05  8:52   ` Yinghai Lu [this message]
2008-09-05 11:45     ` Ingo Molnar

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=86802c440809050152p734f54bex60ae512361d79f93@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dawitbro@sbcglobal.net \
    --cc=hpa@zytor.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jordan.crouse@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®