From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] qemu_arm_vexpress: use latest Linux kernel
Date: Sun, 6 May 2018 21:40:44 +0200 [thread overview]
Message-ID: <20180506214044.786e3dbd@windsurf> (raw)
In-Reply-To: <20180506163059.5801-1-Florian.LaRoche@googlemail.com>
Hello Florian,
Thanks for your contribution.
On Sun, 6 May 2018 18:30:59 +0200, Florian La Roche wrote:
> There should be no reason to keep the qemu_arm_vexpress target
> on an older kernel release, so change this to build with the latest
> Linux kernel release for buildroot.
>
>
> Signed-off-by: Florian La Roche <Florian.LaRoche@googlemail.com>
There is a reason why all defconfigs used a fixed U-Boot / kernel
version: we want those versions to have been tested and confirmed to
work on the target platform.
So, a patch updating to Linux 4.16 would be fine, but not a patch that
changes to automatically use the latest version.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-06 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 16:30 [Buildroot] [PATCH 1/1] qemu_arm_vexpress: use latest Linux kernel Florian La Roche
2018-05-06 19:40 ` Thomas Petazzoni [this message]
2018-05-06 19:58 ` Florian La Roche
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=20180506214044.786e3dbd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox