All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Juraj_=C5=A0arinay_=3Cjuraj=40sarinay=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: netdev@vger.kernel.org, krzk@kernel.org, kuba@kernel.org
Subject: Re: [PATCH net-next v2] net: nfc: Propagate ISO14443 type A target ATS to userspace via netlink
Date: Thu, 07 Nov 2024 09:40:29 +0000	[thread overview]
Message-ID: <173097242925.1585374.10680931770070501247.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241103124525.8392-1-juraj@sarinay.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sun,  3 Nov 2024 13:45:25 +0100 you wrote:
> Add a 20-byte field ats to struct nfc_target and expose it as
> NFC_ATTR_TARGET_ATS via the netlink interface. The payload contains
> 'historical bytes' that help to distinguish cards from one another.
> The information is commonly used to assemble an emulated ATR similar
> to that reported by smart cards with contacts.
> 
> Add a 20-byte field target_ats to struct nci_dev to hold the payload
> obtained in nci_rf_intf_activated_ntf_packet() and copy it to over to
> nfc_target.ats in nci_activate_target(). The approach is similar
> to the handling of 'general bytes' within ATR_RES.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: nfc: Propagate ISO14443 type A target ATS to userspace via netlink
    https://git.kernel.org/netdev/net-next/c/9907cda95fcb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-11-07  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-03 12:45 [PATCH net-next v2] net: nfc: Propagate ISO14443 type A target ATS to userspace via netlink Juraj Šarinay
2024-11-06 10:18 ` Simon Horman
2024-11-06 14:58   ` Juraj Šarinay
2024-11-07  9:31     ` Paolo Abeni
2024-11-07  9:40 ` patchwork-bot+netdevbpf [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=173097242925.1585374.10680931770070501247.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Juraj_=C5=A0arinay_=3Cjuraj=40sarinay=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.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.