From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] configs/solidrun_macchiatobin_marvell: bump component versions
Date: Sun, 16 Sep 2018 10:15:01 +0200 [thread overview]
Message-ID: <20180916101501.5448d307@windsurf> (raw)
In-Reply-To: <20180916042141.4fsryjj54fig2mcc@sapphire.tkos.co.il>
Hello Baruch,
On Sun, 16 Sep 2018 07:21:41 +0300, Baruch Siach wrote:
> > # Kernel
> > BR2_LINUX_KERNEL=y
> > BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> > -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,MarvellEmbeddedProcessors,linux-marvell,linux-4.4.52-armada-17.10)/linux-linux-4.4.52-armada-17.10.tar.gz"
> > +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,MarvellEmbeddedProcessors,linux-marvell,linux-4.4.52-armada-17.10)/linux-linux-4.4.120-armada-18.09.tar.gz"
>
> Why not bump to linux-4.14.22-armada-18.09? Is there any missing functionality
> in that release?
My understanding is that 4.4 is the BSP version that Marvell considers
complete and stable, which has received full QA testing. 4.14 is still
in development, and will be fully ready by the end of the year.
Therefore, in this defconfig using vendor-provided versions of the
components, it probably makes sense to stick to 4.4 for now ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-16 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180914153326.19346-1-thomas.petazzoni@bootlin.com>
[not found] ` <20180914153326.19346-6-thomas.petazzoni@bootlin.com>
2018-09-16 4:21 ` [Buildroot] [PATCH 5/5] configs/solidrun_macchiatobin_marvell: bump component versions Baruch Siach
2018-09-16 8:15 ` Thomas Petazzoni [this message]
2018-09-16 9:31 ` Baruch Siach
2018-10-11 7:32 ` [Buildroot] [PATCH 0/5] Update MacchiatoBin defconfigs Thomas Petazzoni
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=20180916101501.5448d307@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