All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Grund <theflamefire89@gmail.com>
Cc: stable@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: [PATCH 4.9 1/1] LSM: Initialize security_hook_heads upon registration.
Date: Mon, 15 Aug 2022 14:04:30 +0200	[thread overview]
Message-ID: <Yvo2TnrUGoLKEY+v@kroah.com> (raw)
In-Reply-To: <da7d4c6f-0010-6f77-e64e-20f3ebfb57dd@gmail.com>

On Fri, Aug 12, 2022 at 12:50:42PM +0200, Alexander Grund wrote:
> On 11.08.22 14:17, Greg KH wrote:
> > As this fixes no bug or real issue that anyone is having with 4.9, why
> > is this needed?
> 
> This makes it easier to maintain the kernel by removing error-prone code.

Not really, we only add commits that we have to add.  We don't add
things that are "just nice".  Don't do work you don't have to do for a
task right now please.

> I mentioned this patch earlier and you seemed to be interested to at least
> have a look at [1].

Sure, for real bugfixes.  That's not what this patch is.

> The 4.9.y branch is also used by the Civil Infrastructure Project (CIP) to maintain
> a SLTS (Super Long Term Support) 4.4.y branch which is e.g. used by a community
> maintaining alternative Android builds for devices no longer supported by their
> vendors.

Yes, again, I know all about the crazy plans of CIP and my statements on
why it is looney and not a good idea are quite public.  It also has
nothing to do with how we currently maintain the stable/LTS kernel
trees, so it's not relevant to us at all.

thanks,

greg k-h

      reply	other threads:[~2022-08-15 12:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 11:53 [PATCH 4.9 0/1] LSM: Initialize security_hook_heads upon registration Alexander Grund
2022-08-11 11:53 ` [PATCH 4.9 1/1] " Alexander Grund
2022-08-11 12:17   ` Greg KH
2022-08-12 10:50     ` Alexander Grund
2022-08-15 12:04       ` 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=Yvo2TnrUGoLKEY+v@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --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.