All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Dösinger" <stefandoesinger@gmail.com>
To: soc@lists.linux.dev
Cc: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm: zte: defconfig: zx297520v3 defconfig for 7.2
Date: Thu, 14 May 2026 00:21:38 +0300	[thread overview]
Message-ID: <4560997.ejJDZkT8p0@strix> (raw)

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

Hi,

This final pull request adds a defconfig file for zx297520v3 boards. The rationale behind the defconfig is that this board is too underpowered for multi_v7_defconfig and quite odd - it is a Cortex A53 without an FPU running in 32 bit mode.

The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)

are available in the Git repository at:

  https://gitlab.com/stefandoesinger/zx297520-kernel.git tags/zx29-defconfig-for-7.2

for you to fetch changes up to 9afbe04564c59a217c7d1142ce685c4bd951a8d9:

  ARM: zte: defconfig: Add a zx29 defconfig file (2026-05-14 00:04:05 +0300)

----------------------------------------------------------------
ARM: zte: defconfig: zx29 defconfig file for 7.2

The rationale behind the defconfig is that this board is too
underpowered for multi_v7_defconfig and quite odd - it is a Cortex A53
without an FPU running in 32 bit mode.

----------------------------------------------------------------
Stefan Dösinger (1):
      ARM: zte: defconfig: Add a zx29 defconfig file

 arch/arm/configs/zx29_defconfig | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 53 insertions(+)
 create mode 100644 arch/arm/configs/zx29_defconfig

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]

             reply	other threads:[~2026-05-13 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 21:21 Stefan Dösinger [this message]
2026-05-20 19:29 ` [GIT PULL] arm: zte: defconfig: zx297520v3 defconfig for 7.2 Arnd Bergmann

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=4560997.ejJDZkT8p0@strix \
    --to=stefandoesinger@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=soc@lists.linux.dev \
    /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.