From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: Fix memblock_reserve() to include stext
Date: Wed, 31 Jul 2013 19:39:30 +0000 [thread overview]
Message-ID: <20130731193930.GY24642@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CANqRtoR5j2VyRwf0suABfVLxzU30pZndEcCj7uZ2sSrzfGmx_A@mail.gmail.com>
On Thu, Aug 01, 2013 at 04:34:03AM +0900, Magnus Damm wrote:
> Are you aware of any existing fix for this or anyone working on
> solving this issue? If not then I don't mind stepping up. I can
> however think of quite a few other things to do if this has been
> solved already though, so please let me know if you think I should
> focus on fixing this.
I committed a fix for it this morning, so it should be in linux-next by
tomorrow.
next prev parent reply other threads:[~2013-07-31 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 5:58 [PATCH] ARM: Fix memblock_reserve() to include stext Magnus Damm
2013-07-31 9:43 ` Russell King - ARM Linux
2013-07-31 19:34 ` Magnus Damm
2013-07-31 19:39 ` Russell King - ARM Linux [this message]
2013-08-01 7:34 ` Simon Horman
2013-08-01 12:58 ` Paul Gortmaker
2013-08-02 1:32 ` Simon Horman
2013-08-02 3:24 ` Magnus Damm
2013-08-02 9:26 ` Russell King - ARM Linux
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=20130731193930.GY24642@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).