From: Ingo Molnar <mingo@elte.hu>
To: Bernhard Walle <bwalle@suse.de>
Cc: x86@kernel.org, Greg KH <gregkh@suse.de>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
yhlu.kernel@gmail.com, vgoyal@redhat.com
Subject: Re: x86: Add /sys/firmware/memmap
Date: Thu, 3 Jul 2008 16:15:43 +0200 [thread overview]
Message-ID: <20080703141543.GA26416@elte.hu> (raw)
In-Reply-To: <20080627203409.3bc891e3@kopernikus.site>
* Bernhard Walle <bwalle@suse.de> wrote:
> * Greg KH <gregkh@suse.de> [2008-06-27 11:18]:
> >
> > Looks good, want me to take this through my tree (due to the firmware
> > core change)? If so, can you get an ack on the x86 portion from the
> > respective people as well?
>
> Well, the x86 part only applies on tip (because your tree doesn't have
> the e820_{32,64} -> e820 merge). So, wouldn't it easier to ack that
> patch from your side and merge via tip?
Bernhard, i've created a new -tip topic for your changes:
tip/sysfs/firmware-mmap. It is available at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git sysfs/firmware-mmap
This will become a 2-commit topic branch once the dependent x86 bits are
upstream. At that point Greg will be able to pull it from -tip and push
it out via the sysfs tree.
I've added it to the tip/master integration rules to give it testing and
to make sure any subsequent x86 changes stay in sync with the e820 API
changes your patches required.
Ingo
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-07-03 14:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 11:12 x86: Add /sys/firmware/memmap Bernhard Walle
2008-06-27 11:12 ` [PATCH 1/2] " Bernhard Walle
2008-06-27 18:51 ` Dave Hansen
2008-06-27 20:56 ` Greg KH
2008-07-12 0:36 ` Andrew Morton
2008-07-12 22:15 ` firmware/memmap fixes Bernhard Walle
2008-07-12 22:15 ` [PATCH 1/2] firmware/memmap: Cleanup Bernhard Walle
2008-07-12 22:15 ` [PATCH 2/2] firmware/memmap: Move kobject initialisation before kobject_add() Bernhard Walle
2008-06-27 11:12 ` [PATCH 2/2] Use FIRMWARE_MEMMAP on x86/E820 Bernhard Walle
2008-06-27 13:01 ` x86: Add /sys/firmware/memmap Vivek Goyal
2008-06-27 18:18 ` Greg KH
2008-06-27 18:34 ` Bernhard Walle
2008-07-03 14:15 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-26 20:19 Bernhard Walle
2008-06-26 8:14 Bernhard Walle
2008-06-25 19:57 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=20080703141543.GA26416@elte.hu \
--to=mingo@elte.hu \
--cc=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