From: Pavel Machek <pavel@denx.de>
To: sr@denx.de, jwboyer@linux.vnet.ibm.com, robh+dt@kernel.org,
mark.rutland@arm.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au, devicetree@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: trivial@kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] powerpc/sequoia: fix NAND partitions not to overlap
Date: Wed, 17 May 2017 14:06:13 +0200 [thread overview]
Message-ID: <20170517120613.GA583@amd> (raw)
In-Reply-To: <20170402100535.GA18340@amd>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
On Sun 2017-04-02 12:05:36, Pavel Machek wrote:
> Fix overlapping NAND partitions.
>
> Signed-off-by: Pavel Machek <pavel@ucw.cz>
Ping? Two partitions at same place are bad news...
Pavel
> diff --git a/arch/powerpc/boot/dts/sequoia.dts b/arch/powerpc/boot/dts/sequoia.dts
> index b1d3292..e41b88a 100644
> --- a/arch/powerpc/boot/dts/sequoia.dts
> +++ b/arch/powerpc/boot/dts/sequoia.dts
> @@ -229,7 +229,7 @@
> };
> partition@84000 {
> label = "user";
> - reg = <0x00000000 0x01f7c000>;
> + reg = <0x00084000 0x01f7c000>;
> };
> };
> };
>
>
>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-05-17 12:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 10:05 [PATCH] powerpc/sequoia: fix NAND partitions not to overlap Pavel Machek
2017-04-02 10:05 ` Pavel Machek
2017-05-17 12:06 ` Pavel Machek [this message]
2017-05-17 21:37 ` Andrew Morton
2017-05-18 9:48 ` Pavel Machek
2017-05-18 9:48 ` Pavel Machek
2017-05-19 5:50 ` Michael Ellerman
2017-05-19 5:50 ` Michael Ellerman
2017-05-19 9:12 ` Pavel Machek
2017-05-19 9:12 ` Pavel Machek
2017-05-19 10:04 ` Michael Ellerman
2017-05-19 11:18 ` Pavel Machek
2017-05-19 11:18 ` Pavel Machek
2017-05-22 9:12 ` Michael Ellerman
2017-05-22 9:12 ` Michael Ellerman
2017-05-30 9:11 ` Michael Ellerman
2017-05-30 9:11 ` Michael Ellerman
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=20170517120613.GA583@amd \
--to=pavel@denx.de \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=sr@denx.de \
--cc=trivial@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.