From: Vignesh R <vigneshr@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
Santosh Shilimkar <ssantosh@kernel.org>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RESEND] ARM: dts: keystone-k2*: Increase SPI Flash partition size for U-Boot
Date: Wed, 12 Oct 2016 16:40:20 +0530 [thread overview]
Message-ID: <71299871-965f-aef3-7301-4d587430a1a5@ti.com> (raw)
In-Reply-To: <d1a4b59e-5524-9851-425e-5e86e05a593c@oracle.com>
Hi,
On Monday 10 October 2016 09:31 PM, Santosh Shilimkar wrote:
> Vignesh,
>
> On 10/10/2016 7:31 AM, Russell King - ARM Linux wrote:
>> On Mon, Oct 10, 2016 at 07:41:41PM +0530, Vignesh R wrote:
>>> U-Boot SPI Boot image is now more than 512KB for Keystone2 devices and
>>> cannot fit into existing partition. So, increase the SPI Flash partition
>>> for U-Boot to 1MB for all Keystone2 devices.
>>>
>>> Signed-off-by: Vignesh R <vigneshr@ti.com>
>>> ---
>>>
>>> This was submitted to v4.9 merge window but was never picked up:
>>> https://patchwork.kernel.org/patch/9135023/
>
> Another point is, if you want me to pick your patch, please copy
> me next time :-). AFAIK, am seeing this patch in my inbox first time.
>
Sorry, I did address the previous patch to you. Not sure what happened :(
>>
>> I think you need to explain why it's safe to change the layout of the
>> flash partitions like this.
>>
>> - What is this "misc" partition?
>>
>> - Why is it safe to move the "misc" partition in this way?
>>
>> - Do users need to do anything with data stored in the "misc" partition
>> when changing kernels?
>>
>> If the "misc" partition is simply unused space on the flash device, why
>> list it in DT?
>>
> Thanks Russell. Yes, above clarification would be good to get first.
Ok, will send v2 with updated commit message as per my reply in other
thread.
--
Regards
Vignesh
next prev parent reply other threads:[~2016-10-12 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 14:11 Vignesh R
2016-10-10 14:31 ` Russell King - ARM Linux
2016-10-10 16:01 ` Santosh Shilimkar
2016-10-12 11:10 ` Vignesh R [this message]
2016-10-12 11:00 ` Vignesh R
2016-10-12 11:57 ` Russell King - ARM Linux
2016-10-13 12:16 ` Vignesh R
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=71299871-965f-aef3-7301-4d587430a1a5@ti.com \
--to=vigneshr@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®