Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Danilo Bargen <mail@dbrgn.ch>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] configs/pcengines_apu2_defconfig: bump kernel to 5.16
Date: Sat, 22 Jan 2022 13:18:03 +0100	[thread overview]
Message-ID: <20220122131803.7de0d872@windsurf> (raw)
In-Reply-To: <20220120000330.29552850@c3po>

On Thu, 20 Jan 2022 00:03:30 +0100
Danilo Bargen <mail@dbrgn.ch> wrote:

> This fixes the compile errors that were present with the previous
> kernel version (4.19):
> 
> https://gitlab.com/buildroot.org/buildroot/-/jobs/1970084022
> 
> Additionally, the defconfig file was refactored: Configuration
> values are now grouped logically, thus increasing readability and
> maintainability.
> 
> Signed-off-by: Danilo Bargen <mail@dbrgn.ch>

Applied to master, with one change. See below.

> +# Rootfs
>  BR2_TARGET_ROOTFS_EXT2=y
>  BR2_TARGET_ROOTFS_ISO9660=y
>  BR2_TARGET_ROOTFS_ISO9660_BOOT_MENU="board/pcengines/apu2/isolinux.cfg"
>  BR2_TARGET_ROOTFS_ISO9660_HYBRID=y
> -# BR2_TARGET_ROOTFS_TAR is not set

Not clear why you dropped this line. So I re-added it.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-22 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 20:15 [Buildroot] [PATCH 1/1] configs/pcengines_apu2_defconfig: bump kernel to 5.16 Danilo Bargen
2022-01-17 20:06 ` Giulio Benetti
2022-01-19 23:03   ` [Buildroot] [PATCH v2 " Danilo Bargen
2022-01-22 12:18     ` Thomas Petazzoni [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=20220122131803.7de0d872@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=mail@dbrgn.ch \
    /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