All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
	Daniel Borkmann <daniel@iogearbox.net>,
	Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH iproute2-next 3/5] tc: remove eBPF map export and exec bpf import
Date: Thu, 19 Nov 2026 09:35:30 -0800	[thread overview]
Message-ID: <20261119093530.574f9a4e@phoenix.local> (raw)
In-Reply-To: <CAM0EoMnGzNOCBpkXy5A3DXeEjWJwyUbj3As=Htc5E3QWtUXrCg@mail.gmail.com>

On Thu, 19 Nov 2026 04:50:09 -0500
Jamal Hadi Salim <jhs@mojatatu.com> wrote:

> Also, reported by - does that need an email address?

It would have been to have an email to list but there isn't one that means anything.
The OSS scanner just gives
a big report and want to track bug fixes versus original report.

  reply	other threads:[~2026-11-19 17:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  0:15 [PATCH iproute2-next 0/5] bpf: fix mount point parsing and drop the legacy loader Stephen Hemminger
2026-11-19  0:15 ` [PATCH iproute2-next 1/5] lib/bpf: parse /proc/mounts with getmntent and check fs magic Stephen Hemminger
2026-11-19  0:15 ` [PATCH iproute2-next 2/5] lib/fs: " Stephen Hemminger
2026-11-19  0:15 ` [PATCH iproute2-next 3/5] tc: remove eBPF map export and exec bpf import Stephen Hemminger
2026-11-19  9:19   ` Jamal Hadi Salim
2026-11-19  9:50     ` Jamal Hadi Salim
2026-11-19 17:35       ` Stephen Hemminger [this message]
2026-11-19 17:47     ` Stephen Hemminger
2026-11-19 20:12       ` Jamal Hadi Salim
2026-11-19  0:15 ` [PATCH iproute2-next 4/5] lib/bpf: require libbpf and remove legacy ELF loader Stephen Hemminger
2026-11-19  0:15 ` [PATCH iproute2-next 5/5] lib/bpf: check for missing bpf fs mount point Stephen Hemminger
2026-11-19 10:16   ` Toke Høiland-Jørgensen

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=20261119093530.574f9a4e@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=daniel@iogearbox.net \
    --cc=dsahern@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --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.