From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
"Jon Mason" <jonmason@broadcom.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rob Herring" <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: BCM5301X: Specify flash partitions
Date: Thu, 2 Aug 2018 09:16:46 -0700 [thread overview]
Message-ID: <02fbbfbf-81e7-991f-8e37-99d0b6965971@gmail.com> (raw)
In-Reply-To: <20180728121357.13172-1-zajec5@gmail.com>
On 07/28/2018 05:13 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Most devices use Broadcom standard partitions which allows them to be
> described with the "brcm,bcm947xx-cfe-partitions". Exceptions are:
> 1) TP-LINK devices which use "os-image" partition with TRX containing
> kernel only + separated rootfs partition.
> 2) Asus RT-AC87U with custom "asus" partition.
>
> This commit also removes undocumented and unsupported linux,part-probe
> binding which got accidentally upstreamed while describing SPI
> controller.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Applied to devicetree/next, thanks!
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-08-02 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 12:13 [PATCH] ARM: dts: BCM5301X: Specify flash partitions Rafał Miłecki
2018-08-02 16:16 ` Florian Fainelli [this message]
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=02fbbfbf-81e7-991f-8e37-99d0b6965971@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=jonmason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=noltari@gmail.com \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.com \
/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).