From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH v2 00/12] ptxdist and toolchain version bump
Date: Mon, 11 Mar 2019 06:51:18 +0100 [thread overview]
Message-ID: <20190311055118.p6vzxmjmvjicl2wz@pengutronix.de> (raw)
In-Reply-To: <20190310234045.29600-1-rhi@pengutronix.de>
On Mon, Mar 11, 2019 at 12:40:33AM +0100, Roland Hieber wrote:
> v1 -> v2:
> - add gitignore for all old config files
> - formulate the gcc stack clash protection message a bit better
> - bump toolchain to 2018.12 in all platforms
> - sync kernelconfigs
>
> Roland Hieber (12):
> gitignore all old config files
> scripts: add helper to run PTXdist on all platformconfigs
> ptxdist: version bump 2019.02.0 → 2019.03.0
> rpi: toolchain version bump 2018.02 → 2018.12
> rpi: enable gcc stack clash protection
> rpi: sync kernelconfig
> v7a: toolchain version bump 2018.02 → 2018.12
> v7a: enable gcc stack clash protection
> v7a: sync kernelconfig
> v8a: toolchain version bump 2018.02 → 2018.12
> v8a: enable gcc stack clash protection
> v8a: sync kernelconfig
>
> .gitignore | 2 +-
> configs/platform-rpi/kernelconfig | 4 ++--
> configs/platform-rpi/platformconfig | 11 ++++++-----
> configs/platform-v7a/kernelconfig | 4 ++--
> configs/platform-v7a/platformconfig | 11 ++++++-----
> configs/platform-v8a/kernelconfig | 4 ----
> configs/platform-v8a/platformconfig | 11 ++++++-----
> configs/ptxconfig | 13 ++++---------
> scripts/p-all | 6 ++++++
> 9 files changed, 33 insertions(+), 33 deletions(-)
> create mode 100755 scripts/p-all
Series applied to next.
rsc
--
Pengutronix e.K. | Dipl.-Ing. Robert Schwebel |
Industrial Linux Solutions | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
prev parent reply other threads:[~2019-03-11 5:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 23:40 Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 01/12] gitignore all old config files Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 02/12] scripts: add helper to run PTXdist on all platformconfigs Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 03/12] ptxdist: version bump 2019.02.0 → 2019.03.0 Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 04/12] rpi: toolchain version bump 2018.02 → 2018.12 Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 05/12] rpi: enable gcc stack clash protection Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 06/12] rpi: sync kernelconfig Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 07/12] v7a: toolchain version bump 2018.02 → 2018.12 Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 08/12] v7a: enable gcc stack clash protection Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 09/12] v7a: sync kernelconfig Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 10/12] v8a: toolchain version bump 2018.02 → 2018.12 Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 11/12] v8a: enable gcc stack clash protection Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 12/12] v8a: sync kernelconfig Roland Hieber
2019-03-11 5:51 ` Robert Schwebel [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=20190311055118.p6vzxmjmvjicl2wz@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=rhi@pengutronix.de \
/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