Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/ltp-testsuite: bump version to 20210927
Date: Mon, 4 Oct 2021 22:25:56 +0200	[thread overview]
Message-ID: <YVtjVOuYJVeBocYW@pevik> (raw)
In-Reply-To: <20211004221411.1626f3a4@windsurf>

Hi Thomas,

> Hello Petr,

> On Mon, 4 Oct 2021 19:53:38 +0200
> Petr Vorel <petr.vorel@gmail.com> wrote:

> > Kernel headers in all musl versions
> > $ grep LINUX_VERSION_CODE br-test-pkg/*musl*/host/*/sysroot/usr/include/linux/version.h

> > * bootlin-x86-64-musl [1/4]: FAILED
> > * bootlin-armv7-musl [2/4]: FAILED
> > br-test-pkg/bootlin-armv7-musl/host/arm-buildroot-linux-musleabihf/sysroot/usr/include/linux/version.h:#define LINUX_VERSION_CODE 264682
> > br-test-pkg/bootlin-x86-64-musl/host/x86_64-buildroot-linux-musl/sysroot/usr/include/linux/version.h:#define LINUX_VERSION_CODE 264682
> > => 4.9.234  
> > current stable is 4.9.284
> > fix a85cbe6159ff ("uapi: move constants from <linux/kernel.h> to <linux/const.h>")
> > was backported as 834d8b96cd85 in v4.9.250.

> > * bootlin-riscv64-musl [3/4]: FAILED
> > br-test-pkg/bootlin-riscv64-musl/host/riscv64-buildroot-linux-musl/sysroot/usr/include/linux/version.h:#define LINUX_VERSION_CODE 328765
> > => 5.4.61  
> > current stable is 5.4.150
> > fix a85cbe6159ff ("uapi: move constants from <linux/kernel.h> to <linux/const.h>")
> > was backported as 376c3111413c in v5.4.99

> > * br-i386-pentium-mmx-musl [4/4]: OK
> > br-test-pkg/br-i386-pentium-mmx-musl/host/i586-buildroot-linux-musl/sysroot/usr/include/linux/version.h:#define LINUX_VERSION_CODE 264701
> > => 4.9.253 => the only fixed version  

> Ok, so what you need is updates of the kernel headers to the latest dot
> release, within the same kernel headers series.
Yes, the change is in the header. But I'm not sure whether update of kernel headers
requires updating other code (hopefully not).

> > > Except that you did not. So I did it when applying :-)  

> > Thanks! I'm sorry, I forget to amend the commit before sending.

> No worries :-)

Thanks!

Kind regards,
Petr

> Best regards,

> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2021-10-04 20:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 19:00 [Buildroot] [PATCH v2 1/1] package/ltp-testsuite: bump version to 20210927 Petr Vorel
2021-10-03 20:23 ` Thomas Petazzoni
2021-10-04 17:53   ` Petr Vorel
2021-10-04 20:14     ` Thomas Petazzoni
2021-10-04 20:25       ` Petr Vorel [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=YVtjVOuYJVeBocYW@pevik \
    --to=petr.vorel@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.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