Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 19 Jan 2022 14:49:43 +0100
From:   Pavel Machek <pavel@denx.de>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     Pavel Machek <pavel@denx.de>, linux-kernel@vger.kernel.org,
        torvalds@linux-foundation.org, akpm@linux-foundation.org,
        linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
        lkft-triage@lists.linaro.org, jonathanh@nvidia.com,
        f.fainelli@gmail.com, stable@vger.kernel.org
Subject: Re: 4.4 series end of line was Re: [PATCH 4.4 00/17] 4.4.297-rc1
 review
Message-ID: <20220119134943.GA1032@duo.ucw.cz>
References: <20211227151315.962187770@linuxfoundation.org>
 <20220119102858.GB4984@amd>
 <YefooANkr6eem49U@kroah.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU"
Content-Disposition: inline
In-Reply-To: <YefooANkr6eem49U@kroah.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk


--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi!

> > > This is the start of the stable review cycle for the 4.4.297 release.
> > > There are 17 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, plea=
se
> > > let me know.
> >=20
> > 4.4.X series is scheduled for EOL next month. Do you have any
> > estimates if it will be more like Feb 2 or Feb 27?
>=20
> I would bet on Feb 1 :)

Hmm. That does not leave us too much time.

FAQ states:

# Why are some longterm versions supported longer than others?  The
# "projected EOL" dates are not set in stone. Each new longterm kernel
# usually starts with only a 2-year projected EOL that can be extended
# further if there is enough interest from the industry at large to
# help support it for a longer period of time.

Is there anyone else interested in continued 4.4.X maintainence?

CIP project will need to maintain 4.4.X-cip and 4.4.X-cip-rt for some
more years. Do you think it would make sense to maintain 4.4.X-stable
as well? What would be requirements for doing so?

Best regards,
								Pavel
--=20
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

--azLHFNyN32YCQGCU
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRPfPO7r0eAhk010v0w5/Bqldv68gUCYegW9wAKCRAw5/Bqldv6
8i7kAJ4ihbzh6IYNHqBBAq0eKdOiknic/QCeMN2gTepaNuGTiVNfhvT6Ipvt2iY=
=qkFY
-----END PGP SIGNATURE-----

--azLHFNyN32YCQGCU--