From: "Filippo Muscherà" <filippo.muschera@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vme_user: add identifier names to function prototypes
Date: Sat, 7 Feb 2026 19:30:10 +0100 [thread overview]
Message-ID: <aYeCzbrwDeIqYOLh@fedora> (raw)
In-Reply-To: <2026020748-audio-earthling-48d6@gregkh>
On Sat, Feb 07, 2026 at 01:44:02PM +0100, Greg KH wrote:
> - Your patch did not apply to any known trees that Greg is in control
> of. Possibly this is because you made it against Linus's tree, not
> the linux-next tree, which is where all of the development for the
> next version of the kernel is at.
Hi,
I have checked the latest staging-testing tree and I see that these changes
have already been applied by another commit.
Please disregard this patch.
Thanks, Filippo
prev parent reply other threads:[~2026-02-07 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 15:28 [PATCH] staging: vme_user: add identifier names to function prototypes Filippo Muscherà
2026-02-07 12:44 ` Greg KH
2026-02-07 18:30 ` Filippo Muscherà [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=aYeCzbrwDeIqYOLh@fedora \
--to=filippo.muschera@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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