mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: "Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
	"Théo Lebrun" <theo.lebrun@bootlin.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Tawfik Bayouk" <tawfik.bayouk@mobileye.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] MIPS: mobileye: eyeq6h-epm6: Use eyeq6h in the board device tree
Date: Wed, 30 Oct 2024 12:17:31 +0100	[thread overview]
Message-ID: <ZyIVyw2SZ/dKRZsj@alpha.franken.de> (raw)
In-Reply-To: <20241008-eyq6h-dt-v1-1-b8a4df1e6a6c@bootlin.com>

On Tue, Oct 08, 2024 at 11:18:47AM +0200, Gregory CLEMENT wrote:
> There is currently no eyeq6 compatible string defined in the binding
> documentation. Only eyeq6h version is defined, so let's use it.
> 
> Note that there are actually no codes relying on eyeq6h; the purpose
> of this patch is mainly to be coherent with the documentation.
> 
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> ---
>  arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts b/arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts
> index ebc0d363fbf82..59a3e95050eb9 100644
> --- a/arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts
> +++ b/arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts
> @@ -8,7 +8,7 @@
>  #include "eyeq6h.dtsi"
>  
>  / {
> -	compatible = "mobileye,eyeq6-epm6", "mobileye,eyeq6";
> +	compatible = "mobileye,eyeq6h-epm6", "mobileye,eyeq6h";
>  	model = "Mobile EyeQ6H MP6 Evaluation board";
>  
>  	chosen {
> 
> ---
> base-commit: 9852d85ec9d492ebef56dc5f229416c925758edc
> change-id: 20241008-eyq6h-dt-2c4ae1ec1157

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:[~2024-10-30 11:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  9:18 Gregory CLEMENT
2024-10-08  9:25 ` Krzysztof Kozlowski
2024-10-08 10:03   ` Gregory CLEMENT
2024-10-30 11:17 ` 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=ZyIVyw2SZ/dKRZsj@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tawfik.bayouk@mobileye.com \
    --cc=theo.lebrun@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vladimir.kondratiev@mobileye.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

all inboxes | Powered by JetHome®