All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryce <oliverwearzprada@gmail.com>
To: "paul@paul-moore.com" <paul@paul-moore.com>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"linux-audit@redhat.com" <linux-audit@redhat.com>,
	"burn.alting@iinet.net.au" <burn.alting@iinet.net.au>,
	"ast@kernel.org" <ast@kernel.org>,
	"sdf@google.com" <sdf@google.com>
Subject: Re: [PATCH v2] bpf: restore the ebpf program ID for BPF_AUDIT_UNLOAD and PERF_BPF_EVENT_PROG_UNLOAD
Date: Tue, 3 Jan 2023 11:12:18 -0700	[thread overview]
Message-ID: <294DC0E6-5B0C-4ED5-B22C-C6E4A86B0A43@hxcore.ol> (raw)

[-- Attachment #1: Type: text/html, Size: 187732 bytes --]

[-- Attachment #2: Type: text/plain, Size: 107 bytes --]

--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit

             reply	other threads:[~2023-01-04 14:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 18:12 Bryce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-23 18:55 [PATCH v2] bpf: restore the ebpf program ID for BPF_AUDIT_UNLOAD and PERF_BPF_EVENT_PROG_UNLOAD Paul Moore
2022-12-23 18:55 ` Paul Moore
2022-12-23 21:14 ` kernel test robot
2022-12-23 21:14   ` kernel test robot
2022-12-23 21:26 ` Paul Moore
2022-12-23 21:26   ` Paul Moore
2022-12-23 21:44 ` kernel test robot
2022-12-23 21:44   ` kernel test robot
2022-12-24  1:49 ` Stanislav Fomichev
2022-12-24  1:49   ` Stanislav Fomichev
2022-12-24 15:31   ` Paul Moore
2022-12-24 15:31     ` Paul Moore
2022-12-25 22:16   ` Alexei Starovoitov
2022-12-25 22:16     ` Alexei Starovoitov
2022-12-27  3:35     ` Stanislav Fomichev
2022-12-27  3:35       ` Stanislav Fomichev
2022-12-27 16:40       ` Paul Moore
2022-12-27 16:40         ` Paul Moore
2022-12-30  2:13         ` Stanislav Fomichev
2022-12-30  2:13           ` Stanislav Fomichev
2022-12-30  3:10           ` Alexei Starovoitov
2022-12-30  3:10             ` Alexei Starovoitov
2022-12-30  3:38             ` Stanislav Fomichev
2022-12-30  3:38               ` Stanislav Fomichev
2022-12-30  4:18               ` Alexei Starovoitov
2022-12-30  4:18                 ` Alexei Starovoitov
2022-12-27 17:49       ` Alexei Starovoitov
2022-12-27 17:49         ` Alexei Starovoitov
2022-12-28  0:25         ` Stanislav Fomichev
2022-12-28  0:25           ` Stanislav Fomichev
2022-12-25 14:13 ` Jiri Olsa
2022-12-25 14:13   ` Jiri Olsa
2022-12-25 19:14   ` Paul Moore
2022-12-25 19:14     ` Paul Moore
2023-01-03  0:33 ` kernel test robot
2023-01-03  0:33   ` kernel test robot

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=294DC0E6-5B0C-4ED5-B22C-C6E4A86B0A43@hxcore.ol \
    --to=oliverwearzprada@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=burn.alting@iinet.net.au \
    --cc=linux-audit@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=sdf@google.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 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.