From: Johan Hovold <johan@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: alejandroe1@geotab.com, 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 v2 3/3] riscv: dts: sophgo: add zfh for sg2042
Date: Mon, 19 May 2025 15:06:02 +0200 [thread overview]
Message-ID: <aCssur0WxPbFs2HQ@hovoldconsulting.com> (raw)
In-Reply-To: <20250514-saggy-shifter-e4ac7152f823@spud>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
On Wed, May 14, 2025 at 04:49:01PM +0100, Conor Dooley wrote:
> On Wed, May 14, 2025 at 01:55:54PM +0200, Alejandro Enrique via B4 Relay wrote:
> > From: Alejandro Enrique <alejandroe1@geotab.com>
> >
> > Add compatible for u-blox NEO-9M GPS module.
> > --- a/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
> > +++ b/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
> > @@ -22,6 +22,7 @@ properties:
> > - u-blox,neo-6m
> > - u-blox,neo-8
> > - u-blox,neo-m8
> > + - u-blox,neo-m9
>
> No match data in the driver, why is a fallback not sufficient?
By the way, what happened with the Subject in your reply here, Conor?
Johan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-05-19 13:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 11:55 [PATCH 0/2] Add u-blox,neo-m9 compatible Alejandro Enrique via B4 Relay
2025-05-14 11:55 ` [PATCH 1/2] dt-bindings: gnss: add u-blox,neo-9m compatible Alejandro Enrique via B4 Relay
2025-05-14 15:49 ` [PATCH v2 3/3] riscv: dts: sophgo: add zfh for sg2042 Conor Dooley
[not found] ` <CAN=L63qsjEAvfocgP0tGrpe-x6Rx1gvTAkPE9i99Ai2zJj6ssA@mail.gmail.com>
2025-05-15 15:02 ` Conor Dooley
2025-05-16 10:23 ` Alejandro Enrique
2025-05-16 14:01 ` Conor Dooley
2025-05-16 15:00 ` Alejandro Enrique
2025-05-19 12:37 ` Conor Dooley
2025-05-19 12:59 ` Johan Hovold
2025-05-21 16:12 ` Alejandro Enrique
2025-05-19 13:06 ` Johan Hovold [this message]
2025-05-19 15:12 ` Conor Dooley
2025-05-14 11:55 ` [PATCH 2/2] gnss: ubx: add u-blox,neo-m9 compatible Alejandro Enrique via B4 Relay
-- strict thread matches above, loose matches on Subject: below --
2025-05-14 15:15 [PATCH v2 0/3] riscv: dts: sophgo: add more sg2042 isa extension support Han Gao
2025-05-14 15:15 ` [PATCH v2 3/3] riscv: dts: sophgo: add zfh for sg2042 Han Gao
2025-05-15 1:33 ` Chen Wang
2025-05-27 9:34 ` Han Gao
2025-05-27 10:22 ` Chen Wang
2025-05-31 1:34 ` Inochi Amaoto
2025-05-31 2:49 ` Chen Wang
2025-06-06 16:01 ` Conor Dooley
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=aCssur0WxPbFs2HQ@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alejandroe1@geotab.com \
--cc=conor+dt@kernel.org \
--cc=conor@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox