From: Johan Hovold <johan@kernel.org>
To: alejandroe1@geotab.com
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: gnss: add u-blox,neo-9m compatible
Date: Tue, 24 Jun 2025 13:30:22 +0200 [thread overview]
Message-ID: <aFqMTrHOOu10iSQl@hovoldconsulting.com> (raw)
In-Reply-To: <20250523-ubx-m9-v3-1-6fa4ef5b7d4a@geotab.com>
On Fri, May 23, 2025 at 01:19:52PM +0200, Alejandro Enrique via B4 Relay wrote:
> From: Alejandro Enrique <alejandroe1@geotab.com>
>
> Add compatible for u-blox NEO-9M GPS module.
>
> Signed-off-by: Alejandro Enrique <alejandroe1@geotab.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.
> ---
> Changes in v3:
> - Remove unnecessary example, 'items', and blank line in the devicetree binding
> - Link to v2: https://lore.kernel.org/r/20250522-ubx-m9-v2-1-6ecd470527bc@geotab.com
>
> Changes in v2:
> - Modify the binding to allow falling back to neo-m8
> - Remove compatible string from u-blox driver
> - Link to v1: https://lore.kernel.org/r/20250514-ubx-m9-v1-0-193973a4f3ca@geotab.com
Now applied, thanks.
Johan
prev parent reply other threads:[~2025-06-24 11:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 11:19 [PATCH v3] dt-bindings: gnss: add u-blox,neo-9m compatible Alejandro Enrique
2025-05-23 11:19 ` Alejandro Enrique via B4 Relay
2025-05-23 11:52 ` Krzysztof Kozlowski
2025-05-27 6:27 ` Krzysztof Kozlowski
2025-05-27 11:54 ` Alejandro Enrique
2025-05-27 8:35 ` Krzysztof Kozlowski
2025-05-27 10:44 ` Johan Hovold
2025-05-27 10:51 ` Krzysztof Kozlowski
2025-05-27 11:02 ` Johan Hovold
2025-05-27 11:14 ` Krzysztof Kozlowski
2025-05-27 17:33 ` Rob Herring
2025-05-27 17:33 ` Rob Herring (Arm)
2025-06-24 11:30 ` Johan Hovold [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=aFqMTrHOOu10iSQl@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alejandroe1@geotab.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.