linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/4] kexec: (bugfix) calc correct end address of memory ranges in device tree
Date: Mon, 1 Aug 2016 13:52:41 +0900	[thread overview]
Message-ID: <20160801045240.GD7995@linaro.org> (raw)
In-Reply-To: <20160729172356.GD1041@n2100.armlinux.org.uk>

On Fri, Jul 29, 2016 at 06:23:56PM +0100, Russell King - ARM Linux wrote:
> On Fri, Jul 29, 2016 at 10:12:26AM -0700, Geoff Levand wrote:
> > On Fri, 2016-07-29 at 09:27 +0100, Russell King - ARM Linux wrote:
> > 
> > > So, these functions are a mess and need fixing.
> > 
> > Since this change isn't really related to arm64 support, I'll
> > drop this patch from my series.
> 
> Do you have a case which triggers bugs in this code?

Actually, this patch was necessary when my kdump used "usable-memory"
properties in "memory" nodes, as on ppc64, to limit the usable memory
regions that can be used by crash dump kernel.
Since then, I've moved to the approach of using "mem=" kernel parameter,
then introducing a new property, "linux,usable-memory-range," under /chosen
and now we don't need this patch any more.

So, we can drop it but I still believe that it is buggy.

Thanks,
-Takahiro AKASHI

> -- 
> RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
> according to speedtest.net.

  reply	other threads:[~2016-08-01  4:52 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 23:28 [PATCH v1 0/4] arm64 kexec-tools patches Geoff Levand
2016-07-19 23:28 ` [PATCH v1 4/4] arm64: Add support for binary image files Geoff Levand
2016-07-19 23:28 ` [PATCH v1 1/4] kexec: (bugfix) calc correct end address of memory ranges in device tree Geoff Levand
2016-07-27 22:45   ` Thiago Jung Bauermann
2016-07-27 23:23     ` Russell King - ARM Linux
2016-07-28 23:54       ` Thiago Jung Bauermann
2016-07-29  8:27         ` Russell King - ARM Linux
2016-07-29 17:12           ` Geoff Levand
2016-07-29 17:23             ` Russell King - ARM Linux
2016-08-01  4:52               ` AKASHI Takahiro [this message]
2016-09-06  0:29                 ` Memory range end be inclusive or exclusive? " AKASHI Takahiro
2016-10-31  8:50                   ` AKASHI Takahiro
2016-11-07  8:17                     ` Simon Horman
2016-07-19 23:28 ` [PATCH v1 3/4] arm64: Add arm64 kexec support Geoff Levand
2016-07-20 15:39   ` Mark Rutland
2016-07-20 19:19     ` Geoff Levand
2016-07-21 10:31       ` Mark Rutland
2016-07-21 10:50         ` Robin Murphy
2016-07-21 21:49           ` Geoff Levand
2016-07-22  4:08             ` Pratyush Anand
2016-07-22  5:33               ` AKASHI Takahiro
2016-07-22  9:54               ` Mark Rutland
2016-07-22 10:03               ` Robin Murphy
2016-07-22 13:56                 ` Pratyush Anand
2016-07-22 17:59                   ` Robin Murphy
2016-07-25 21:56                 ` Geoff Levand
2016-07-20 17:53   ` Pratyush Anand
2016-07-20 20:33     ` Geoff Levand
2016-07-20 20:54   ` [PATCH v1.2 " Geoff Levand
2016-07-22  7:12     ` AKASHI Takahiro
2016-07-26  0:37       ` Geoff Levand
2016-07-25 14:28     ` Ruslan Bilovol
2016-07-25 20:50       ` Geoff Levand
2016-07-26  1:36         ` Ruslan Bilovol
2016-07-26  8:16           ` AKASHI Takahiro
2016-07-26 21:26             ` Ruslan Bilovol
2016-07-26 21:54               ` Geoff Levand
2016-07-19 23:28 ` [PATCH v1 2/4] kexec: Add common device tree routines Geoff Levand
2016-07-22  7:19   ` AKASHI Takahiro
2016-07-27 18:11     ` Geoff Levand
2016-07-20  4:30 ` [PATCH v1 0/4] arm64 kexec-tools patches AKASHI Takahiro
2016-07-26 23:05 ` Simon Horman
2016-07-27  5:57   ` AKASHI Takahiro
2016-07-28 18:09   ` Geoff Levand
2016-07-29  0:31     ` Simon Horman

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=20160801045240.GD7995@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --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).