The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
	"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>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Cc: 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: Tue, 08 Oct 2024 12:03:20 +0200	[thread overview]
Message-ID: <871q0qewt3.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <f7f6e582-6e68-4f45-b486-43132b896856@kernel.org>

Krzysztof Kozlowski <krzk@kernel.org> writes:

> On 08/10/2024 11:18, 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(-)
>> 
>
> That's a new platform, so you were supposed to make it warning free. I
> think that dtbs_check were never really run here...

Yes my bad. Sorry for that I won't do it again.

>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Thanks!

>
> Best regards,
> Krzysztof

  reply	other threads:[~2024-10-08 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  9:18 [PATCH] MIPS: mobileye: eyeq6h-epm6: Use eyeq6h in the board device tree Gregory CLEMENT
2024-10-08  9:25 ` Krzysztof Kozlowski
2024-10-08 10:03   ` Gregory CLEMENT [this message]
2024-10-30 11:17 ` Thomas Bogendoerfer

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=871q0qewt3.fsf@BLaptop.bootlin.com \
    --to=gregory.clement@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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=tsbogend@alpha.franken.de \
    --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