public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>,
	jan.kiszka@siemens.com
Cc: isar-users@googlegroups.com, cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [next] iwg20m: add support for this board
Date: Fri, 07 Jun 2019 15:41:09 +0100	[thread overview]
Message-ID: <1559918469.21054.3.camel@codethink.co.uk> (raw)
In-Reply-To: <20190606074829.8104-2-daniel.sangorrin@toshiba.co.jp>

On Thu, 2019-06-06 at 16:48 +0900, Daniel Sangorrin wrote:
> This patch adds support for the iwg20m board to isar-cip-core.
> 
> - Kernel version notes
> 
> This board is only supported by the 4.4 kernel. For that
> reason, the preferred version is set to 4.4 and the user
> doesn't need to specify :opt-4.4.yml
[...]

This really shouldn't be allowed to happen.  All the patches applied to
4.4-cip to support this board were already upstream, so this must be a
regression.  If this board is used as a basis for real systems that
need to run beyond EOL of the 4.4-cip branch (~2026), it needs to be
possible to upgrade them to a new kernel version at that time.

Ben.

-- 
Ben Hutchings, Software Developer                         Codethink Ltd
https://www.codethink.co.uk/                 Dale House, 35 Dale Street
                                     Manchester, M1 2HF, United Kingdom

  parent reply	other threads:[~2019-06-07 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  7:48 iwg20m with preferred kernel set to 4.4 Daniel Sangorrin
2019-06-06  7:48 ` [next] iwg20m: add support for this board Daniel Sangorrin
2019-06-06  9:09   ` Jan Kiszka
2019-06-07 14:41   ` Ben Hutchings [this message]
2019-06-07 15:06     ` [cip-dev] " Chris Paterson
2019-06-07 15:16       ` Ben Hutchings
2019-06-06  7:55 ` iwg20m with preferred kernel set to 4.4 daniel.sangorrin

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=1559918469.21054.3.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.org \
    --cc=daniel.sangorrin@toshiba.co.jp \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox