Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Matyukevich <geomatsi@gmail.com>
To: buildroot@buildroot.org
Cc: Joao Pinto <jpinto@synopsys.com>,
	ARC Maintainers <arc-buildroot@synopsys.com>,
	Sergey Matyukevich <geomatsi@gmail.com>
Subject: [Buildroot] [PATCH 0/5] synopsys: boards maintenance
Date: Mon, 31 Jan 2022 11:12:09 +0300	[thread overview]
Message-ID: <20220131081214.12773-1-geomatsi@gmail.com> (raw)

Hi all,

This is a maintenance patch series for Synopsys boards. Outdated
and unused VDK configurations are removed. All the other boards
receive Linux kernel and U-Boot updates.

Regards,
Sergey


Sergey Matyukevich (5):
  configs/snps_arc700_axs101: bump kernel and u-boot versions
  configs/snps_archs32_axs103: bump kernel and u-boot versions
  configs/snps_archs38_hsdk: bump kernel and u-boot versions
  configs/snps_archs38_haps: bump kernel and u-boot versions
  board/synopsys: remove outdated vdk boards

 board/synopsys/axs10x/uboot-fragment.config   |   1 +
 .../synopsys/vdk/linux-vdk-aarch64-defconfig  | 143 ------------------
 board/synopsys/vdk/readme.txt                 |  65 --------
 configs/snps_aarch64_vdk_defconfig            |  12 --
 configs/snps_arc700_axs101_defconfig          |  10 +-
 configs/snps_archs38_axs103_defconfig         |  10 +-
 configs/snps_archs38_haps_defconfig           |   6 +-
 configs/snps_archs38_hsdk_defconfig           |   7 +-
 configs/snps_archs38_vdk_defconfig            |  20 ---
 9 files changed, 20 insertions(+), 254 deletions(-)
 create mode 100644 board/synopsys/axs10x/uboot-fragment.config
 delete mode 100644 board/synopsys/vdk/linux-vdk-aarch64-defconfig
 delete mode 100644 board/synopsys/vdk/readme.txt
 delete mode 100644 configs/snps_aarch64_vdk_defconfig
 delete mode 100644 configs/snps_archs38_vdk_defconfig

-- 
2.35.0

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

             reply	other threads:[~2022-01-31  8:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31  8:12 Sergey Matyukevich [this message]
2022-01-31  8:12 ` [Buildroot] [PATCH 1/5] configs/snps_arc700_axs101: bump kernel and u-boot versions Sergey Matyukevich
2022-02-07 10:07   ` [Buildroot] [arc-buildroot] " Alexey Brodkin via buildroot
2022-01-31  8:12 ` [Buildroot] [PATCH 2/5] configs/snps_archs32_axs103: " Sergey Matyukevich
2022-02-07 10:08   ` [Buildroot] [arc-buildroot] " Alexey Brodkin via buildroot
2022-01-31  8:12 ` [Buildroot] [PATCH 3/5] configs/snps_archs38_hsdk: " Sergey Matyukevich
2022-02-07 10:09   ` [Buildroot] [arc-buildroot] " Alexey Brodkin via buildroot
2022-01-31  8:12 ` [Buildroot] [PATCH 4/5] configs/snps_archs38_haps: " Sergey Matyukevich
2022-02-07 10:09   ` [Buildroot] [arc-buildroot] " Alexey Brodkin via buildroot
2022-01-31  8:12 ` [Buildroot] [PATCH 5/5] board/synopsys: remove outdated vdk boards Sergey Matyukevich
2022-02-07 10:11   ` [Buildroot] [arc-buildroot] " Alexey Brodkin via buildroot
2022-01-31 12:05 ` [Buildroot] [PATCH 0/5] synopsys: boards maintenance Giulio Benetti
2022-01-31 13:09   ` Sergey Matyukevich
2022-01-31 13:10     ` Giulio Benetti
2022-02-12 11:53 ` Arnout Vandecappelle

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=20220131081214.12773-1-geomatsi@gmail.com \
    --to=geomatsi@gmail.com \
    --cc=arc-buildroot@synopsys.com \
    --cc=buildroot@buildroot.org \
    --cc=jpinto@synopsys.com \
    /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