From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Carpenter <error27@gmail.com>
Cc: LiuJunyuan <2058432396@qq.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vme_user: handle zero image size in read/write
Date: Wed, 21 Oct 2026 08:16:15 +0200 [thread overview]
Message-ID: <2026102154-osmosis-cubical-0695@gregkh> (raw)
In-Reply-To: <athV4vUa3aZDDlAX@stanley.mountain>
On Wed, Oct 21, 2026 at 09:04:18AM +0300, Dan Carpenter wrote:
> We removed the requirement that AI patches need to a special tag.
>
> Generally, staging is just for practice writing code so it doesn't
> make sense to use AI, but I was asking Greg to merge AI security fixes
> like this so we'll see how persuasive I was. :) The vme_user code is
> full of way more serious security issues and probably we should just
> delete it.
I agree, we should just delete it at this point in time. I'll gladly
take a patch for that.
thanks,
greg k-h
prev parent reply other threads:[~2026-10-21 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 3:41 LiuJunyuan
2026-10-21 6:02 ` Dan Carpenter
2026-10-21 6:04 ` Dan Carpenter
2026-10-21 6:16 ` Greg KH [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=2026102154-osmosis-cubical-0695@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=2058432396@qq.com \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.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®