From: Geliang Tang <geliang@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [6.6.y] "selftests/bpf: Add netkit to tc_redirect selftest" needs to be reverted
Date: Fri, 26 Apr 2024 18:12:22 +0800 [thread overview]
Message-ID: <e890da3e6b47059a496f743623800223282d7984.camel@kernel.org> (raw)
In-Reply-To: <2024042610-tiring-overdue-a6b5@gregkh>
cc stable@vger.kernel.org
On Fri, 2024-04-26 at 10:50 +0200, Greg Kroah-Hartman wrote:
> Hi,
>
> This is the friendly email-bot of Greg Kroah-Hartman's inbox. I've
> detected that you have sent him a direct question that might be
> better
> sent to a public mailing list which is much faster in responding to
> questions than Greg normally is.
>
> Please try asking one of the following mailing lists for your
> questions:
>
> For udev and hotplug related questions, please ask on the
> linux-hotplug@vger.kernel.org mailing list
>
> For USB related questions, please ask on the
> linux-usb@vger.kernel.org
> mailing list
>
> For PCI related questions, please ask on the
> linux-pci@vger.kernel.org or linux-kernel@vger.kernel.org mailing
> lists
>
> For serial and tty related questions, please ask on the
> linux-serial@vger.kernel.org mailing list.
>
> For staging tree related questions, please ask on the
> linux-staging@lists.linux.dev mailing list.
>
> For general kernel related questions, please ask on the
> kernelnewbies@nl.linux.org or linux-kernel@vger.kernel.org mailing
> lists, depending on the type of question. More basic, beginner
> questions are better asked on the kernelnewbies list, after reading
> the wiki at www.kernelnewbies.org.
>
> For Linux stable and longterm kernel release questions or patches
> to
> be included in the stable or longterm kernel trees, please email
> stable@vger.kernel.org and Cc: the linux-kernel@vger.kernel.org
> mailing list so all of the stable kernel developers can be
> notified.
> Also please read Documentation/process/stable-kernel-rules.rst in
> the
> Linux kernel tree for the proper procedure to get patches accepted
> into the stable or longterm kernel releases.
>
> If you really want to ask Greg the question, please read the
> following
> two links as to why emailing a single person directly is usually not
> a
> good thing, and causes extra work on a single person:
> http://www.arm.linux.org.uk/news/?newsitem=11
> http://www.eyrie.org/~eagle/faqs/questions.html
>
> After reading those messages, and you still feel that you want to
> email
> Greg instead of posting on a mailing list, then resend your message
> within 24 hours and it will go through to him. But be forewarned,
> his
> email inbox currently looks like:
> 912 messages in /home/greg/mail/INBOX/
> so it might be a while before he gets to the message.
>
> Thank you for your understanding.
>
> The email triggering this response has been automatically discarded.
>
> thanks,
>
> greg k-h's email bot
next parent reply other threads:[~2024-04-26 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ea05dcf2a0417aa2068a4dfa61bd562a6e8127d6.camel@kernel.org>
[not found] ` <2024042610-tiring-overdue-a6b5@gregkh>
2024-04-26 10:12 ` Geliang Tang [this message]
2024-04-26 10:21 ` [6.6.y] "selftests/bpf: Add netkit to tc_redirect selftest" needs to be reverted Greg Kroah-Hartman
2024-04-26 10:22 ` Geliang Tang
2024-04-29 10:59 ` Greg Kroah-Hartman
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=e890da3e6b47059a496f743623800223282d7984.camel@kernel.org \
--to=geliang@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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