All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: akuster808 <akuster808@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Worries kernels supported
Date: Fri, 5 Apr 2019 19:42:39 -0400	[thread overview]
Message-ID: <CADkTA4MT3JctYMTFjLZXtJYgaxj6HG=G_nAAe+w0A-JRGXRFxw@mail.gmail.com> (raw)
In-Reply-To: <cfd56541-43c4-5128-3d41-cddc356a3cb8@gmail.com>

On Thu, Apr 4, 2019 at 5:28 PM akuster808 <akuster808@gmail.com> wrote:
>
> Hello,
>
> I noticed there are 3 kernels in Warrior. 4.18, 4.19 an 5.0. Do we
> really need 4.18?
> I see its the default version for poky-tiny. 4.18 is EOL but maintained
> by Windriver.

4.18 needed to be around through M3 to backstop some layers and references
that were being updated.

I may delete it as part of M4, but really, since I kept it through M3, I may not
churn it in M4.  I handle all the support load on the linux-yocto
reference kernels,
so it shouldn't cause any one harm one way or the other.

I keep a very close eye on the versions, so nothing is around by chance or
by mistake .. and best to just copy me on the email, since I can
easily miss them
in the noise.

Bruce

>
> regards,
> Armin
>
>
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


  parent reply	other threads:[~2019-04-05 23:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 21:28 Worries kernels supported akuster808
2019-04-05 21:54 ` [OE-core] " Khem Raj
2019-04-05 21:54   ` Khem Raj
2019-04-06 16:51   ` Manjukumar Harthikote Matha
2019-04-05 23:42 ` Bruce Ashfield [this message]
2019-04-05 23:44   ` Bruce Ashfield
2019-04-06  0:04   ` akuster808

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='CADkTA4MT3JctYMTFjLZXtJYgaxj6HG=G_nAAe+w0A-JRGXRFxw@mail.gmail.com' \
    --to=bruce.ashfield@gmail.com \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yocto@yoctoproject.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 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.