public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: Petr Hodina <petr.hodina@protonmail.com>,
	biemster <l.j.beemster@gmail.com>,
	netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	oe-linux-nfc@lists.linux.dev, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH QUESTION 0/2] NFC support in Linux (and support for Qualcomm SDM845 devices)
Date: Mon, 23 Mar 2026 23:56:23 +0100	[thread overview]
Message-ID: <9cb387c2-5690-44aa-a5ad-0416d6bb3374@ixit.cz> (raw)
In-Reply-To: <eb316800-0be6-4aa7-b9f6-e2b17646d1a0@kernel.org>

> 
> You will not get another stack, but taking care of Linux nfc and neard
> would be appreciated.

Just tested with `neard`, `nfctool -d nfc0 -p` and the HW is able to detect tag 
(didn't do more testing for now, but it's good start).

Thank you for the new release!

I'll send non-QUESTION series ~ tomorrow.

David

> 
> Let me release a new version for it.
> 
> Best regards,
> Krzysztof

-- 
David Heidelberg


  reply	other threads:[~2026-03-23 22:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-22 14:24 [PATCH QUESTION 0/2] NFC support in Linux (and support for Qualcomm SDM845 devices) David Heidelberg via B4 Relay
2026-03-22 14:24 ` [PATCH QUESTION 1/2] arm64: dts: qcom: sdm845-oneplus: Enable NFC David Heidelberg via B4 Relay
2026-03-23 11:35   ` Konrad Dybcio
2026-03-23 11:56   ` Krzysztof Kozlowski
2026-03-22 14:24 ` [PATCH QUESTION 2/2] arm64: dts: qcom: sdm845-shift-axolotl: " David Heidelberg via B4 Relay
2026-03-22 19:48 ` [PATCH QUESTION 0/2] NFC support in Linux (and support for Qualcomm SDM845 devices) Krzysztof Kozlowski
2026-03-23 22:56   ` David Heidelberg [this message]
2026-03-23 11:34 ` Konrad Dybcio

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=9cb387c2-5690-44aa-a5ad-0416d6bb3374@ixit.cz \
    --to=david@ixit.cz \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=l.j.beemster@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oe-linux-nfc@lists.linux.dev \
    --cc=petr.hodina@protonmail.com \
    --cc=phone-devel@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