devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: sboyd@kernel.org, robh+dt@kernel.org, john@phrozen.org,
	gregkh@linuxfoundation.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
	devel@driverdev.osuosl.org, neil@brown.name,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 5/6] staging: mt7621-dts: use valid vendor 'mediatek' instead of invalid 'mtk'
Date: Tue, 9 Mar 2021 16:07:29 +0100	[thread overview]
Message-ID: <20210309150729.GA12267@alpha.franken.de> (raw)
In-Reply-To: <20210309052226.29531-6-sergio.paracuellos@gmail.com>

On Tue, Mar 09, 2021 at 06:22:25AM +0100, Sergio Paracuellos wrote:
> Vendor listed for mediatek in kernel vendor file 'vendor-prefixes.yaml'
> contains 'mediatek' as a valid vendor string. Some nodes in the device
> tree are using an invalid vendor string vfor 'mtk' instead. Fix all of
> them in dts file. Update also ralink mt7621 related code to properly
> match new strings. Even there are used in the device tree there are
> some strings that are not referred anywhere but have been also updated
> with new vendor name. These are 'mtk,mt7621-wdt', 'mtk,mt7621-nand',
> 'mtk,mt7621-mc', and 'mtk,mt7621-cpc'.
> 
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
>  arch/mips/ralink/mt7621.c              |  6 +++---

Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

Thomas.

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

  reply	other threads:[~2021-03-09 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  5:22 [PATCH v11 0/6] MIPS: ralink: add CPU clock detection and clock driver for MT7621 Sergio Paracuellos
2021-03-09  5:22 ` [PATCH v11 1/6] dt-bindings: clock: add dt binding header for mt7621 clocks Sergio Paracuellos
2021-04-09 18:15   ` Stephen Boyd
2021-03-09  5:22 ` [PATCH v11 2/6] dt: bindings: add mt7621-sysc device tree binding documentation Sergio Paracuellos
2021-04-09 18:15   ` Stephen Boyd
2021-03-09  5:22 ` [PATCH v11 3/6] clk: ralink: add clock driver for mt7621 SoC Sergio Paracuellos
2021-04-09 18:14   ` Stephen Boyd
2021-04-09 18:34     ` Sergio Paracuellos
2021-03-09  5:22 ` [PATCH v11 4/6] staging: mt7621-dts: make use of new 'mt7621-clk' Sergio Paracuellos
2021-03-09  5:22 ` [PATCH v11 5/6] staging: mt7621-dts: use valid vendor 'mediatek' instead of invalid 'mtk' Sergio Paracuellos
2021-03-09 15:07   ` Thomas Bogendoerfer [this message]
2021-03-09  5:22 ` [PATCH v11 6/6] MAINTAINERS: add MT7621 CLOCK maintainer Sergio Paracuellos
2021-03-23  8:13 ` [PATCH v11 0/6] MIPS: ralink: add CPU clock detection and clock driver for MT7621 Sergio Paracuellos

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=20210309150729.GA12267@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=john@phrozen.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sergio.paracuellos@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).