From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH v1 1/2] MIPS: ath79: ar9331_dpt_module: update led nodes
Date: Fri, 15 May 2020 10:10:46 +0200 [thread overview]
Message-ID: <20200515081046.GA8653@alpha.franken.de> (raw)
In-Reply-To: <20200510060324.25134-1-o.rempel@pengutronix.de>
On Sun, May 10, 2020 at 08:03:23AM +0200, Oleksij Rempel wrote:
> Fit led nodes to the latest naming schema.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> arch/mips/boot/dts/qca/ar9331_dpt_module.dts | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
both patches 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 ]
prev parent reply other threads:[~2020-05-15 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 6:03 [PATCH v1 1/2] MIPS: ath79: ar9331_dpt_module: update led nodes Oleksij Rempel
2020-05-10 6:03 ` [PATCH v1 2/2] MIPS: ath79: ar9331: rename uart to serial node Oleksij Rempel
2020-05-15 8:10 ` 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=20200515081046.GA8653@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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