[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dfd63c64-184e-4e48-9344-a3db0612036b@kernel.org>
Date: Fri, 23 May 2025 13:52:06 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: alejandroe1@...tab.com, Johan Hovold <johan@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v3] dt-bindings: gnss: add u-blox,neo-9m compatible
On 23/05/2025 13:19, Alejandro Enrique via B4 Relay wrote:
> From: Alejandro Enrique <alejandroe1@...tab.com>
>
> Add compatible for u-blox NEO-9M GPS module.
>
> Signed-off-by: Alejandro Enrique <alejandroe1@...tab.com>
> ---
> This series just add the compatible string for u-blox NEO-9M module,
> using neo-m8 as fallback. I have tested the driver with such a module
> and it is working fine.
> ---
I assume there is a user somewhere?
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
<form letter>
This is an automated instruction, just in case, because many review tags
are being ignored. If you know the process, you can skip it (please do
not feel offended by me posting it here - no bad intentions intended).
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
of patchset, under or above your Signed-off-by tag, unless patch changed
significantly (e.g. new properties added to the DT bindings). Tag is
"received", when provided in a message replied to you on the mailing
list. Tools like b4 can help here. However, there's no need to repost
patches *only* to add the tags. The upstream maintainer will do that for
tags received on the version they apply.
Full context and explanation:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
</form letter>
Best regards,
Krzysztof
Powered by blists - more mailing lists