All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herve Jourdain <herve.jourdain@neuf.fr>
To: 'Khem Raj' <raj.khem@gmail.com>, yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][PATCH 1/1] linux-raspberrypi_4.7.bb: upgrade to latest good version
Date: Sun, 20 Nov 2016 13:58:36 +0100	[thread overview]
Message-ID: <003e01d2432d$d42d17c0$7c874740$@neuf.fr> (raw)
In-Reply-To: <29ca6996-3502-26ef-fc30-a04e7fd97814@gmail.com>

Hi Khem,

If I may, I have an interest in keeping 4.7 for a few more months (2 or 3 I
guess).
I'm using it for a few things, and I don't currently plan to switch to 4.8,
but rather to 4.9 when it's more stable (hence the 2 or 3 additional
months).
As you already know, 4.9 is supposed to be the next LTS (if Greg
Kroah-Hartman doesn't change his mind), and I'd like to wait for it while
keep using the version I already use.

This said, given the recent rebasing on the raspberrypi github, at least for
version 4.7, it definitely is a maintenance burden.
If that can help, I'm volunteering to maintain the revision for the 4.7
raspberrypi linux kernel, for the next 2 to 3 months.

After that, the question that will remain is what revisions do we keep: we
currently have 4.1, 4.4, 4.7 and 4.8.
We will soon have 4.9.
4.1 and 4.4 are LTS (EOL = 09/2017 & 02/2018), neither 4.7 nor 4.8 will be,
and 4.9 is supposed to be.
What do you think we should do, scrap 4.1 and 4.7, leaving 4.4, 4.8 and 4.9?
Or keep only the LTS ones?

Herve

-----Original Message-----
From: Khem Raj [mailto:raj.khem@gmail.com] 
Sent: jeudi 17 novembre 2016 18:17
To: Herve Jourdain <herve.jourdain@neuf.fr>; yocto@yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi][PATCH 1/1] linux-raspberrypi_4.7.bb:
upgrade to latest good version



On 11/17/16 5:13 AM, Herve Jourdain wrote:
> Signed-off-by: Herve Jourdain <herve.jourdain@neuf.fr>
> ---
>  recipes-kernel/linux/linux-raspberrypi_4.7.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.7.bb 
> b/recipes-kernel/linux/linux-raspberrypi_4.7.bb
> index 0315f8f..4a8fe36 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_4.7.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_4.7.bb
> @@ -1,8 +1,8 @@
>  FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>  
> -LINUX_VERSION ?= "4.7.7"
> +LINUX_VERSION ?= "4.7.10"

I think, we should abandon all non-lts recipes except one which will be
latest release ( 4.8 ) as of today.

>  
> -SRCREV = "a45a35c08598b23f9fd82e49c83b46c7d536244f"
> +SRCREV = "e7fa325a40f260ed9fb86391a0b65150eba8c112"
>  SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.7.y \
>             file://0001-fix-dtbo-rules.patch \  "
> 




  reply	other threads:[~2016-11-20 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 13:13 [meta-raspberrypi][PATCH 0/1] linux-raspberrypi_4.7.bb: upgrade to latest good version Herve Jourdain
2016-11-17 13:13 ` [meta-raspberrypi][PATCH 1/1] " Herve Jourdain
2016-11-17 17:17   ` Khem Raj
2016-11-20 12:58     ` Herve Jourdain [this message]
2016-11-20 19:32       ` Khem Raj

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='003e01d2432d$d42d17c0$7c874740$@neuf.fr' \
    --to=herve.jourdain@neuf.fr \
    --cc=raj.khem@gmail.com \
    --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.