From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, roberto.sassu@huaweicloud.com,
bpf@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] bpf/umd possible deadcode
Date: Mon, 27 Jan 2025 13:55:53 +0000 [thread overview]
Message-ID: <Z5eQaeG92S5K8J7I@gallifrey> (raw)
In-Reply-To: <20241114022400.301175-1-linux@treblig.org>
* linux@treblig.org (linux@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
>
> Hi,
> I'm not 100% sure about these, since I'm not quite
> sure how to test it properly.
>
> As far as I can tell the UMD isn't needed by bpf itself
> any more; so I've got one patch that just removes that select.
> But then that leaves no users of umd itself; and I split that
> separately since I saw there was still some discussion this year
> on other uses.
Hi,
Does anyone have any views on this pair?
Thanks,
Dave
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
>
> Dave
>
> Dr. David Alan Gilbert (2):
> bpf: Don't select USERMODE_DRIVER
> umd: Remove
>
> include/linux/usermode_driver.h | 19 ----
> kernel/Makefile | 1 -
> kernel/bpf/preload/Kconfig | 5 -
> kernel/usermode_driver.c | 191 --------------------------------
> 4 files changed, 216 deletions(-)
> delete mode 100644 include/linux/usermode_driver.h
> delete mode 100644 kernel/usermode_driver.c
>
> --
> 2.47.0
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
prev parent reply other threads:[~2025-01-27 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 2:23 [PATCH 0/2] bpf/umd possible deadcode linux
2024-11-14 2:23 ` [PATCH 1/2] bpf: Don't select USERMODE_DRIVER linux
2024-11-14 2:24 ` [PATCH 2/2] umd: Remove linux
2025-01-27 13:55 ` Dr. David Alan Gilbert [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=Z5eQaeG92S5K8J7I@gallifrey \
--to=linux@treblig.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=roberto.sassu@huaweicloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox