linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Paul Burton" <paulburton@kernel.org>,
	"Jonas Gorski" <jonas.gorski@gmail.com>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] mips: bmips: fix and improve reboot nodes
Date: Tue, 6 Apr 2021 15:02:45 +0200	[thread overview]
Message-ID: <20210406130245.GD9505@alpha.franken.de> (raw)
In-Reply-To: <20210314164351.24665-1-noltari@gmail.com>

On Sun, Mar 14, 2021 at 05:43:45PM +0100, Álvaro Fernández Rojas wrote:
> These patches improve bmips bcm63xx device tree nodes.
> 
> v2: add missing BCM63268 patch.
> 
> Álvaro Fernández Rojas (6):
>   mips: bmips: fix syscon-reboot nodes
>   mips: bmips: bcm6328: populate device tree nodes
>   mips: bmips: bcm6358: populate device tree nodes
>   mips: bmips: bcm6362: populate device tree nodes
>   mips: bmips: bcm6368: populate device tree nodes
>   mips: bmips: bcm63268: populate device tree nodes
> 
>  arch/mips/boot/dts/brcm/bcm3368.dtsi  |   2 +-
>  arch/mips/boot/dts/brcm/bcm63268.dtsi | 132 +++++++++++++++++++++++---
>  arch/mips/boot/dts/brcm/bcm6328.dtsi  | 119 ++++++++++++++++++++---
>  arch/mips/boot/dts/brcm/bcm6358.dtsi  |  85 ++++++++++++++---
>  arch/mips/boot/dts/brcm/bcm6362.dtsi  | 129 ++++++++++++++++++++++---
>  arch/mips/boot/dts/brcm/bcm6368.dtsi  | 129 ++++++++++++++++++++++---
>  6 files changed, 530 insertions(+), 66 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2021-04-06 13:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14 16:43 [PATCH v2 0/6] mips: bmips: fix and improve reboot nodes Álvaro Fernández Rojas
2021-03-14 16:43 ` [PATCH v2 1/6] mips: bmips: fix syscon-reboot nodes Álvaro Fernández Rojas
2021-03-30 17:02   ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 2/6] mips: bmips: bcm6328: populate device tree nodes Álvaro Fernández Rojas
2021-03-30 17:07   ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 3/6] mips: bmips: bcm6358: " Álvaro Fernández Rojas
2021-03-30 17:09   ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 4/6] mips: bmips: bcm6362: " Álvaro Fernández Rojas
2021-03-30 17:10   ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 5/6] mips: bmips: bcm6368: " Álvaro Fernández Rojas
2021-03-30 17:11   ` Florian Fainelli
2021-03-14 16:43 ` [PATCH v2 6/6] mips: bmips: bcm63268: " Álvaro Fernández Rojas
2021-03-30 17:13   ` Florian Fainelli
2021-03-30 13:09 ` [PATCH v2 0/6] mips: bmips: fix and improve reboot nodes Thomas Bogendoerfer
2021-03-30 17:14   ` Florian Fainelli
2021-04-06 13:02 ` Thomas Bogendoerfer [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=20210406130245.GD9505@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=noltari@gmail.com \
    --cc=paulburton@kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).