From: Al Viro <viro@zeniv.linux.org.uk>
To: Gabriel Ramos <maguraa53@gmail.com>
Cc: andrew@lunn.ch, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: remove obsolete network and 16-bit video drivers
Date: Sun, 14 Jun 2026 05:28:34 +0100 [thread overview]
Message-ID: <20260614042834.GO2636677@ZenIV> (raw)
In-Reply-To: <20260614021629.656478-1-maguraa53@gmail.com>
On Sat, Jun 13, 2026 at 11:16:29PM -0300, Gabriel Ramos wrote:
> From: Gabriel Ramos Barbosa Mota <maguraa53@gmail.com>
>
> These drivers are currently in the staging tree and have been identified as unmaintained and obsolete. They lack modern hardware support, do not integrate with the current device model, and represent technical debt. This patch removes these drivers to clean up the staging area and reduce the overall maintenance burden, as there is no evidence of active users or ongoing development for these specific components. Signed-off-by: Gabriel Ramos <maguraa53@gmail.com>
> ---
> teste_disco.img | Bin 0 -> 20971520 bytes
> 1 file changed, 0 insertions(+), 0 deletions(-)
> create mode 100644 teste_disco.img
>
> diff --git a/teste_disco.img b/teste_disco.img
> new file mode 100644
> index 0000000000000000000000000000000000000000..13145eb3ecf765e330220f06cf8ad7553c3d9ff2
> GIT binary patch
[snip]
What this patch does is dropping a 20Mb binary into top-level
directory, apparently with empty (and dirty) ext4 image in it
(according to debugfs, that is).
WTF?
next prev parent reply other threads:[~2026-06-14 4:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 2:16 [PATCH] staging: remove obsolete network and 16-bit video drivers Gabriel Ramos
2026-06-14 4:28 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-14 2:20 Gabriel Ramos
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=20260614042834.GO2636677@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=andrew@lunn.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=maguraa53@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox