mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sean Young <sean@mess.org>
Cc: linux-kernel@vger.kernel.org, andrii@kernel.org,
	eddyz87@gmail.com, ihor.solodrai@linux.dev, ast@kernel.org,
	daniel@iogearbox.net, memxor@gmail.com, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	emil@etsalapatis.com, shuah@kernel.org, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3] selftests/bpf: convert lirc_mode2 to prog_tests and extend coverage
Date: Sun, 30 Aug 2026 11:00:06 +0000	[thread overview]
Message-ID: <178808760617.3314773.13243773534139324133.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260820214332.89030-1-sean@mess.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Thu, 20 Aug 2026 22:43:29 +0100 you wrote:
> While porting, extend coverage of the BPF_LIRC_MODE2 attach/detach/
> query API:
> 
>  - bpf_prog_attach() with invalid flags is rejected with -EINVAL
>    and does not attach the program
>  - bpf_prog_query() with invalid flags is rejected with -EINVAL
>    without disturbing existing attachments
>  - bpf_prog_query() reports the correct program id, not just count,
>    at each step, via bpf_prog_get_info_by_fd()
>  - a lirc chardev can hold more than one attached program: load a
>    second, independent instance, attach it alongside the first,
>    confirm both are reported by bpf_prog_query(), then detach it
>    without disturbing the first program's attachment
>  - detaching an already-detached program consistently fails with
>    -ENOENT, for both the first and second program
> 
> [...]

Here is the summary with links:
  - [v3] selftests/bpf: convert lirc_mode2 to prog_tests and extend coverage
    https://git.kernel.org/bpf/bpf-next/c/d761934c9483

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



      parent reply	other threads:[~2026-08-30 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 21:43 Sean Young
2026-08-20 22:34 ` bot+bpf-ci
2026-08-30 11:00 ` 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=178808760617.3314773.13243773534139324133.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=sean@mess.org \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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®