From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] toolchain: update AArch32/AArch64 toolchains to 8-2-2019.01
Date: Tue, 29 Jan 2019 13:40:01 +0200 [thread overview]
Message-ID: <87tvhrzo8e.fsf@tarshish> (raw)
In-Reply-To: <20190129102608.4k3wfli3dyomb7aa@debby>
Hi Joakim,
On Tue, Jan 29 2019, Joakim Bech wrote:
> So after looking a bit more into the git log of how patches where
> created in the past it looks like I should create 4 patches, "pseudo git
> log -4".
> - toolchain-external: update Arm ARM 8.2-2019.01
> - toolchain-external: update Arm AArch64-BE toolchain 8.2-2019.01
> - toolchain-external: update Arm AArch64 toolchain 8.2-2019.01
> - toolchain: add necessary options to support 5.0 kernel headers
The v5.0 headers patch should be the first in the series. Otherwise the
toolchains will be selecting a non existing config symbol which hurts
bisectability.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2019-01-29 11:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190128133500.7515-1-joakim.bech@linaro.org>
2019-01-28 14:02 ` [Buildroot] [PATCH 1/1] toolchain: update AArch32/AArch64 toolchain to 8-2-2019.01 Joakim Bech
2019-01-28 14:08 ` Thomas Petazzoni
2019-01-28 14:35 ` Joakim Bech
2019-01-28 14:59 ` Thomas Petazzoni
2019-01-28 16:41 ` Joakim Bech
2019-01-28 17:05 ` [Buildroot] [PATCH v2 1/1] toolchain: update AArch32/AArch64 toolchains " Joakim Bech
2019-01-28 22:22 ` Arnout Vandecappelle
2019-01-29 10:26 ` Joakim Bech
2019-01-29 11:27 ` Arnout Vandecappelle
2019-01-29 11:34 ` Arnout Vandecappelle
2019-01-29 12:00 ` Joakim Bech
2019-02-04 10:08 ` Peter Korsgaard
2019-02-04 12:42 ` Arnout Vandecappelle
2019-02-04 16:10 ` Peter Korsgaard
2019-01-29 11:55 ` Joakim Bech
2019-01-29 11:40 ` Baruch Siach [this message]
2019-01-29 11:50 ` Joakim Bech
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=87tvhrzo8e.fsf@tarshish \
--to=baruch@tkos.co.il \
--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.