From: patchwork-bot+netdevbpf@kernel.org
To: Johan Hovold <johan@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] nfc: refactor USB endpoint lookups
Date: Wed, 01 Apr 2026 02:30:12 +0000 [thread overview]
Message-ID: <177501061229.3039405.10122971974982249905.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260330103655.1672331-1-johan@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Mar 2026 12:36:52 +0200 you wrote:
> Use the common USB helper for looking up bulk and interrupt endpoints
> instead of open coding.
>
> Johan
>
>
> Johan Hovold (3):
> nfc: nfcmrvl: refactor endpoint lookup
> nfc: pn533: refactor endpoint lookup
> nfc: port100: refactor endpoint lookup
>
> [...]
Here is the summary with links:
- [1/3] nfc: nfcmrvl: refactor endpoint lookup
https://git.kernel.org/netdev/net-next/c/dba69cba4a5d
- [2/3] nfc: pn533: refactor endpoint lookup
https://git.kernel.org/netdev/net-next/c/13f2e141b944
- [3/3] nfc: port100: refactor endpoint lookup
https://git.kernel.org/netdev/net-next/c/771a627ddd3b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-01 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 10:36 [PATCH 0/3] nfc: refactor USB endpoint lookups Johan Hovold
2026-03-30 10:36 ` [PATCH 1/3] nfc: nfcmrvl: refactor endpoint lookup Johan Hovold
2026-03-30 10:36 ` [PATCH 2/3] nfc: pn533: " Johan Hovold
2026-03-30 10:36 ` [PATCH 3/3] nfc: port100: " Johan Hovold
2026-04-01 2:30 ` 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=177501061229.3039405.10122971974982249905.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.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.