From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Grund <theflamefire89@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [GIT 4.9] LSM,security,selinux,smack: Backport of LSM changes
Date: Sun, 10 Jul 2022 13:06:48 +0200 [thread overview]
Message-ID: <YsqyxydY1kbufgng@kroah.com> (raw)
In-Reply-To: <81f96354-cbed-26e4-9f3f-5287095ccece@gmail.com>
On Sun, Jul 10, 2022 at 12:44:34PM +0200, Alexander Grund wrote:
> > Please just send them to us in patch form like all other stable
> > submissions.
>
> Sorry I'm new to this kernel list. I'll send 1 patch of this series in a new mail (as a test).
> Please bear with me if there are any mistakes, the next ones will then be better.
As my bot says, this is all documented:
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
Make sure the patches you are submitting follows those rules on what is
able to be accepted.
> The Civil Infrastructure Platform (CIP) e.g. maintains LTS kernel trees which are now End of Life but still used.
> They call that SLTS ("Super Long Term Support") and there is e.g. a 4.4.y branch with backports from the 4.9.y LTS branch.
> That kernel is e.g. used in many Android phones.
What 4.4.y Android devices are still supported by their vendors? And
are they still getting kernel updates?
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-10 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 12:07 [GIT 4.9] LSM,security,selinux,smack: Backport of LSM changes Alexander Grund
2022-07-09 12:16 ` Greg KH
2022-07-10 10:44 ` Alexander Grund
2022-07-10 11:06 ` Greg KH [this message]
2022-07-10 12:38 ` Alexander Grund
2022-07-10 12:48 ` Greg KH
2022-07-10 13:02 ` Alexander Grund
2022-07-10 13:23 ` Greg KH
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=YsqyxydY1kbufgng@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.