From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] support/testing: add atop test
Date: Wed, 30 Jan 2019 09:03:01 +0100 [thread overview]
Message-ID: <20190130090301.1736f95d@windsurf> (raw)
In-Reply-To: <5c510deba126a_42713fb91e0de6f447919@ultri5.mail>
Hello,
On Wed, 30 Jan 2019 00:37:31 -0200
Ricardo Martincoski <ricardo.martincoski@gmail.com> wrote:
> No. My mistake, sorry.
> I should had used the prebuilt armv7 kernel.
> I guess I can remove all lines from BR2_TARGET_GENERIC_GETTY_PORT to
> BR2_LINUX_KERNEL_INTREE_DTS_NAME.
>
> I was (wrongly) pretty sure we always use prebuilt kernel 3.11.0 .
> That's because all *-run.log for the python test cases.
>
> This new version of atop needs kernel headers >= 3.14.
> So I decided to not take the risk of having weird behaviors using an older (than
> 3.14) kernel.
> Then I saw that the rust test case compiles kernel 4.x and decided to do the
> same. I just copied the current kernel version from qemu_arm_vexpress_defconfig.
>
> What I missed is that only the armv5 prebuilt kernel is 3.11.0 . The armv7 one
> is 4.0.0 (as we can see on all *-run.log for the perl test cases) and therefore
> it should work here.
OK. We could actually switch the armv5 prebuilt kernel to a newer
kernel version as well.
> Should I send a followup patch switching to prebuilt kernel?
Yes, please. It makes the test case a lot faster to build/test.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-30 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 2:14 [Buildroot] [PATCH 1/2] package/atop: bump to version 2.4.0 Ricardo Martincoski
2019-01-28 2:14 ` [Buildroot] [PATCH 2/2] support/testing: add atop test Ricardo Martincoski
2019-01-28 9:03 ` Peter Korsgaard
2019-01-28 11:34 ` Ricardo Martincoski
2019-01-29 21:25 ` Thomas Petazzoni
2019-01-30 2:37 ` Ricardo Martincoski
2019-01-30 8:03 ` Thomas Petazzoni [this message]
2019-01-28 9:02 ` [Buildroot] [PATCH 1/2] package/atop: bump to version 2.4.0 Peter Korsgaard
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=20190130090301.1736f95d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.