All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: buildroot@buildroot.org
Cc: Luca Ceresoli <luca@lucaceresoli.net>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Leon Anavi <leon.anavi@konsulko.com>,
	Jagan Teki <jagan@amarulasolutions.com>
Subject: [Buildroot] [PATCH 0/8] Olimex boards u-boot/linux update
Date: Fri, 22 Oct 2021 00:00:15 +0200	[thread overview]
Message-ID: <20211021220023.68288-1-giulio.benetti@benettiengineering.com> (raw)

This patchset enable on olinuxino_a10/a13 the NEON support while the rest
of patches bump uboot and linux versions. I've been able to test all
boards except a10. A64 bump will follow.

Giulio Benetti (8):
  configs/olimex_a10_olinuxino: bump to Linux kernel 5.14.13 and u-boot
    2021.10
  configs/olimex_a10_olinuxino: use FPU NEON strategy
  configs/olimex_a13_olinuxino: bump to Linux kernel 5.14.13 and u-boot
    2021.10
  configs/olimex_a13_olinuxino: use FPU NEON strategy
  configs/olimex_a20_olinuxino_lime2: bump to Linux kernel 5.14.13 and
    u-boot 2021.10
  configs/olimex_a20_olinuxino_lime: bump to Linux kernel 5.14.13 and
    u-boot 2021.10
  configs/olimex_a20_olinuxino_micro: bump to Linux kernel 5.14.13 and
    u-boot 2021.10
  configs/olimex_a33_olinuxino: bump to Linux kernel 5.14.13 and u-boot
    2021.10

 configs/olimex_a10_olinuxino_lime_defconfig  | 9 +++++----
 configs/olimex_a13_olinuxino_defconfig       | 9 +++++----
 configs/olimex_a20_olinuxino_lime2_defconfig | 8 ++++----
 configs/olimex_a20_olinuxino_lime_defconfig  | 8 ++++----
 configs/olimex_a20_olinuxino_micro_defconfig | 8 ++++----
 configs/olimex_a33_olinuxino_defconfig       | 8 ++++----
 6 files changed, 26 insertions(+), 24 deletions(-)

-- 
2.25.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2021-10-21 22:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 22:00 Giulio Benetti [this message]
2021-10-21 22:00 ` [Buildroot] [PATCH 1/8] configs/olimex_a10_olinuxino: bump to Linux kernel 5.14.13 and u-boot 2021.10 Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 2/8] configs/olimex_a10_olinuxino: use FPU NEON strategy Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 3/8] configs/olimex_a13_olinuxino: bump to Linux kernel 5.14.13 and u-boot 2021.10 Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 4/8] configs/olimex_a13_olinuxino: use FPU NEON strategy Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 5/8] configs/olimex_a20_olinuxino_lime2: bump to Linux kernel 5.14.13 and u-boot 2021.10 Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 6/8] configs/olimex_a20_olinuxino_lime: " Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 7/8] configs/olimex_a20_olinuxino_micro: " Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 8/8] configs/olimex_a33_olinuxino: " Giulio Benetti
2021-10-24 14:09 ` [Buildroot] [PATCH 0/8] Olimex boards u-boot/linux update Thomas Petazzoni
2021-10-24 14:40   ` Giulio Benetti
2021-10-25 12:28     ` Giulio Benetti

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=20211021220023.68288-1-giulio.benetti@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=buildroot@buildroot.org \
    --cc=jagan@amarulasolutions.com \
    --cc=leon.anavi@konsulko.com \
    --cc=luca@lucaceresoli.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.