public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: cedric_hombourger@mentor.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v5 0/5] linux-custom recipe rework
Date: Thu, 19 Dec 2019 07:19:53 -0800 (PST)	[thread overview]
Message-ID: <e77b22e5-cec7-48ba-92f6-21701b69c73e@googlegroups.com> (raw)
In-Reply-To: <cover.1576002128.git.jan.kiszka@siemens.com>


[-- Attachment #1.1: Type: text/plain, Size: 3750 bytes --]



On Tuesday, December 10, 2019 at 7:22:11 PM UTC+1, Jan Kiszka wrote:
>
> Adopting Cedric patches, removing the qemu-user trick for now, re-adding 
> test cases for the config fragments and bumping the kernel to 4.19.88. 
>  
>

All looks good to me. Thanks Jan for all the help!
Would be good to get this reviewed (and merged?) before the Xmas break

CI tests look good so far. I tested a functionally identical version 
> against jailhouse-images earlier already. 
>
> Jan 
>
>
> CC: Cedric Hombourger <Cedric_H...@mentor.com <javascript:>> 
>
> Cedric Hombourger (4): 
>   recipes-kernel/linux: make KERNEL_DEFCONFIG support in-tree defconfigs 
>   linux-mainline: fix stripping of .0 from the kernel version 
>   linux-mainline: update from 4.19.0 to 4.19.88 
>   linux-custom: rewrite to no longer depend on the kernel's builddeb 
>
> Jan Kiszka (1): 
>   linux-mainline: Test config fragments 
>
>  RECIPE-API-CHANGELOG.md                            |   8 + 
>  doc/custom_kernel.md                               |  83 ++++++++ 
>  .../recipes-kernel/linux/files/no-root-nfs.cfg     |   1 + 
>  .../recipes-kernel/linux/files/no-ubifs-fs.cfg     |   1 + 
>  .../recipes-kernel/linux/linux-mainline_4.19.0.bb  |  22 --- 
>  .../recipes-kernel/linux/linux-mainline_4.19.88.bb |  33 ++++ 
>  meta/recipes-kernel/linux/files/build-kernel.sh    | 129 ------------- 
>  meta/recipes-kernel/linux/files/debian/compat      |   1 + 
>  .../recipes-kernel/linux/files/debian/control.tmpl |  37 ++++ 
>  .../linux/files/debian/isar/build.tmpl             |  45 +++++ 
>  .../linux/files/debian/isar/clean.tmpl             |  21 +++ 
>  .../linux/files/debian/isar/common.tmpl            |  50 +++++ 
>  .../linux/files/debian/isar/install.tmpl           | 192 
> +++++++++++++++++++ 
>  .../linux/files/debian/isar/version.cfg.tmpl       |   2 + 
>  .../linux/files/debian/linux-image.postinst.tmpl   |  29 +++ 
>  .../linux/files/debian/linux-image.postrm.tmpl     |  35 ++++ 
>  .../linux/files/debian/linux-image.preinst.tmpl    |  25 +++ 
>  .../linux/files/debian/linux-image.prerm.tmpl      |  21 +++ 
>  meta/recipes-kernel/linux/files/debian/rules.tmpl  |  39 ++++ 
>  meta/recipes-kernel/linux/linux-custom.inc         | 209 
> +++++++++++++++------ 
>  20 files changed, 778 insertions(+), 205 deletions(-) 
>  create mode 100644 doc/custom_kernel.md 
>  create mode 100644 meta-isar/recipes-kernel/linux/files/no-root-nfs.cfg 
>  create mode 100644 meta-isar/recipes-kernel/linux/files/no-ubifs-fs.cfg 
>  delete mode 100644 meta-isar/recipes-kernel/linux/
> linux-mainline_4.19.0.bb 
>  create mode 100644 meta-isar/recipes-kernel/linux/
> linux-mainline_4.19.88.bb 
>  delete mode 100644 meta/recipes-kernel/linux/files/build-kernel.sh 
>  create mode 100644 meta/recipes-kernel/linux/files/debian/compat 
>  create mode 100644 meta/recipes-kernel/linux/files/debian/control.tmpl 
>  create mode 100644 meta/recipes-kernel/linux/files/debian/isar/build.tmpl 
>  create mode 100644 meta/recipes-kernel/linux/files/debian/isar/clean.tmpl 
>  create mode 100644 
> meta/recipes-kernel/linux/files/debian/isar/common.tmpl 
>  create mode 100644 
> meta/recipes-kernel/linux/files/debian/isar/install.tmpl 
>  create mode 100644 
> meta/recipes-kernel/linux/files/debian/isar/version.cfg.tmpl 
>  create mode 100644 
> meta/recipes-kernel/linux/files/debian/linux-image.postinst.tmpl 
>  create mode 100644 
> meta/recipes-kernel/linux/files/debian/linux-image.postrm.tmpl 
>  create mode 100644 
> meta/recipes-kernel/linux/files/debian/linux-image.preinst.tmpl 
>  create mode 100644 
> meta/recipes-kernel/linux/files/debian/linux-image.prerm.tmpl 
>  create mode 100755 meta/recipes-kernel/linux/files/debian/rules.tmpl 
>
> -- 
> 2.16.4 
>
>

[-- Attachment #1.2: Type: text/html, Size: 6515 bytes --]

      parent reply	other threads:[~2019-12-19 15:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 18:22 Jan Kiszka
2019-12-10 18:22 ` [PATCH v5 1/5] recipes-kernel/linux: make KERNEL_DEFCONFIG support in-tree defconfigs Jan Kiszka
2019-12-10 18:22 ` [PATCH v5 2/5] linux-mainline: fix stripping of .0 from the kernel version Jan Kiszka
2019-12-10 18:22 ` [PATCH v5 3/5] linux-mainline: update from 4.19.0 to 4.19.88 Jan Kiszka
2019-12-10 18:22 ` [PATCH v5 4/5] linux-custom: rewrite to no longer depend on the kernel's builddeb Jan Kiszka
2019-12-11 14:40   ` Jan Kiszka
2019-12-11 15:20   ` Gylstorff Quirin
2019-12-11 15:43     ` Jan Kiszka
2019-12-11 18:36       ` Jan Kiszka
2019-12-11 22:09         ` Henning Schild
2019-12-12  7:57           ` Gylstorff Quirin
2019-12-12  8:01             ` Jan Kiszka
2019-12-12  9:46               ` Gylstorff Quirin
2019-12-12 10:10                 ` Gylstorff Quirin
2019-12-10 18:22 ` [PATCH v5 5/5] linux-mainline: Test config fragments Jan Kiszka
2019-12-19 15:19 ` cedric_hombourger [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=e77b22e5-cec7-48ba-92f6-21701b69c73e@googlegroups.com \
    --to=cedric_hombourger@mentor.com \
    --cc=isar-users@googlegroups.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