From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Grund <theflamefire89@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.9 1/1] security,selinux,smack: kill security_task_wait hook
Date: Sat, 23 Jul 2022 16:47:13 +0200 [thread overview]
Message-ID: <YtwJ8WvRl0TolEAs@kroah.com> (raw)
In-Reply-To: <f5b1e4e6-28bb-9c92-8939-e49db8cba0dd@gmail.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Sat, Jul 23, 2022 at 10:37:10AM +0200, Alexander Grund wrote:
> Hi Greg,
>
> after the previous discussion about what kind of patches are acceptable for stable
> and your hints on how to send them to the ML in https://lore.kernel.org/all/YsrfDfe3urGkepvJ@kroah.com/
> I'd like to know if this patch meets the requirements and if it can be considered.
Yes, it is now queued up. It was delayed due to the RETBLEED mess.
> I do have a few more similar ones which I think meet the stable requirements
> and finally the init-cleanup patch
> (upstream 3dfc9b02864bt "LSM: Initialize security_hook_heads upon registration.")
> which I'd like to backport to 4.9. But first I want to know whether I now got
> the formal requirements right before sending further patches.
Let's see what the other patches look like, I can't guarantee anything
without reviewing them first.
thanks,
greg k-h
prev parent reply other threads:[~2022-07-23 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 9:56 [PATCH 4.9 0/1] security,selinux,smack: kill security_task_wait hook Alexander Grund
2022-07-11 9:56 ` [PATCH 4.9 1/1] " Alexander Grund
2022-07-23 8:37 ` Alexander Grund
2022-07-23 14:47 ` 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=YtwJ8WvRl0TolEAs@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=theflamefire89@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.