From: David Heidelberg <david@ixit.cz>
To: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
oe-linux-nfc@lists.linux.dev
Subject: [pull-request] NFC updates for net-next 2026-06-11
Date: Thu, 11 Jun 2026 20:44:34 +0200 [thread overview]
Message-ID: <1aed7555-3d24-413c-b284-bc85fdd33055@ixit.cz> (raw)
The following changes since commit 518d8d0199538a4d6d5e51064044ece71e0c42e7:
net: sched: avoid printing uninitialized link speed (2026-06-11 15:44:55 +0200)
are available in the Git repository at:
https://codeberg.org/linux-nfc/linux.git tags/nfc-net-next-20260611
for you to fetch changes up to 1b92c1f6d6d87f9ec3c2bef3c68b99b097712f9a:
MAINTAINERS: Update address for David Heidelberg (2026-06-11 20:24:47 +0200)
----------------------------------------------------------------
NFC updates for net-next 20260611
- nxp-nci: Add ISO15693 support
- nxp-nci: treat -ENXIO in IRQ thread as no data available
- nci: uart: Constify struct tty_ldisc_ops
- trf7970a: fix comment typos
- Use named initializers for struct i2c_device_id
- MAINTAINERS: Update address for David Heidelberg
----------------------------------------------------------------
Carl Lee (2):
nfc: nxp-nci: Add ISO15693 support
nfc: nxp-nci: treat -ENXIO in IRQ thread as no data available
Christophe JAILLET (1):
nfc: nci: uart: Constify struct tty_ldisc_ops
David Heidelberg (1):
MAINTAINERS: Update address for David Heidelberg
Miles Krause (1):
nfc: trf7970a: fix comment typos
Uwe Kleine-König (The Capable Hub) (1):
nfc: Use named initializers for struct i2c_device_id
MAINTAINERS | 2 +-
drivers/nfc/microread/i2c.c | 2 +-
drivers/nfc/nfcmrvl/i2c.c | 4 ++--
drivers/nfc/nxp-nci/core.c | 1 +
drivers/nfc/nxp-nci/i2c.c | 12 ++++++++++--
drivers/nfc/pn533/i2c.c | 4 ++--
drivers/nfc/pn544/i2c.c | 4 ++--
drivers/nfc/s3fwrn5/i2c.c | 4 ++--
drivers/nfc/st-nci/i2c.c | 4 ++--
drivers/nfc/st21nfca/i2c.c | 4 ++--
drivers/nfc/trf7970a.c | 6 +++---
net/nfc/nci/uart.c | 2 +-
12 files changed, 29 insertions(+), 20 deletions(-)
next reply other threads:[~2026-06-11 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 18:44 David Heidelberg [this message]
2026-06-12 0:10 ` patchwork-bot+netdevbpf
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=1aed7555-3d24-413c-b284-bc85fdd33055@ixit.cz \
--to=david@ixit.cz \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®