From: Bernhard Walle <bwalle@suse.de>
To: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: x86: move dma32_reserve_bootmem() after reserve_crashkernel()
Date: Sun, 27 Jul 2008 00:25:59 +0200 [thread overview]
Message-ID: <20080727002559.48cee0d4@kopernikus.site> (raw)
Hi Ingo,
can you send 91467bdf6e53058af13fd255375d6634ba0c70e0 (in
x86/crashdump) to Linus still for 2.6.27? I want that also in stable
for 2.6.26, and Greg KH stated that it must be first in Linus' tree.
(Although that commit cannot be applied to -stable directly because of
the huge code unification in 2.6.27 on the x86 side.)
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
next reply other threads:[~2008-07-26 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 22:25 Bernhard Walle [this message]
2008-07-28 15:25 ` Ingo Molnar
2008-07-28 16:01 ` 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=20080727002559.48cee0d4@kopernikus.site \
--to=bwalle@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®