From: Bernhard Walle <bwalle@suse.de>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs()
Date: Fri, 11 Jul 2008 17:09:15 +0200 [thread overview]
Message-ID: <20080711170915.727c3e36@halley.suse.de> (raw)
In-Reply-To: <20080710232834.GG11227@verge.net.au>
* Simon Horman [2008-07-11 09:28]:
>
> I'm using crosstool. I guess its crazy enough to show up things like this.
Ah! Maybe I should install that too, but since we have 5
architectures in our build system natively, I always use that infra
structure to test my builds ...
> These problems do indeed seem to be fixed now, I have applied all
> three patches.
Thanks!
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-07-11 15:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 23:06 Use /sys/firmware/memmap in kexec Bernhard Walle
2008-07-06 23:06 ` [PATCH 1/5] Remove trailing whitespace Bernhard Walle
2008-07-07 7:02 ` Simon Horman
2008-07-06 23:06 ` [PATCH 2/5] Fix compiler warning in kexec-x86.c Bernhard Walle
2008-07-07 7:03 ` Simon Horman
2008-07-06 23:06 ` [PATCH 3/5] Parse /sys/firmware/memmap Bernhard Walle
2008-07-07 7:06 ` Simon Horman
2008-07-07 14:43 ` Bernhard Walle
2008-07-07 14:43 ` [PATCH 1/3] " Bernhard Walle
2008-07-07 14:43 ` [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs() Bernhard Walle
2008-07-09 0:41 ` Simon Horman
2008-07-09 11:10 ` Parse /sys/firmware/memmap Bernhard Walle
2008-07-09 11:11 ` [PATCH 1/3] " Bernhard Walle
2008-07-10 23:29 ` Simon Horman
2008-07-09 11:11 ` [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs() Bernhard Walle
2008-07-09 11:11 ` [PATCH 3/3] Use get_memory_ranges() on x86-64 Bernhard Walle
2008-07-09 11:12 ` [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs() Bernhard Walle
[not found] ` <20080710232834.GG11227@verge.net.au>
2008-07-11 15:09 ` Bernhard Walle [this message]
2008-07-07 14:43 ` [PATCH 3/3] Use get_memory_ranges() on x86-64 Bernhard Walle
2008-07-06 23:06 ` [PATCH 4/5] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs() Bernhard Walle
2008-07-06 23:06 ` [PATCH 5/5] Use get_memory_ranges() on x86-64 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=20080711170915.727c3e36@halley.suse.de \
--to=bwalle@suse.de \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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