From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v2 0/3] arm64: meson: Add SoC ID detection for G12A
Date: Tue, 12 Mar 2019 13:25:23 -0700 [thread overview]
Message-ID: <7hlg1ju9fw.fsf@baylibre.com> (raw)
In-Reply-To: <20190307140147.22047-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> This patchset :
> - Fixes the package id detection for S905 variants and AXG packages
> - Adds new SoC IDs and Packages IDs for G12A/G12B, and S805X/Y
> - Adds Add AO Secure node for G12A dtsi
>
> Changes since v1:
> - Added G12B S922X package ID
> - Added G12A S905D2 package ID
> - Fixed patch 2 commit message
Series queued for v5.2.
> Neil Armstrong (3):
> soc: amlogic: gx-socinfo: Add mask for each SoC packages
> soc: amlogic: gx-socinfo: Add new SoC IDs and Packages IDs
Applied to branch: v5.2/drivers.
> arm64: dts: meson-g12a: Add AO Secure node
Applied to v5.2/dt64,
Thanks for all the new SoC detection!
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-03-13 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 14:01 [PATCH v2 0/3] arm64: meson: Add SoC ID detection for G12A Neil Armstrong
2019-03-07 14:01 ` [PATCH v2 1/3] soc: amlogic: gx-socinfo: Add mask for each SoC packages Neil Armstrong
2019-03-07 14:01 ` [PATCH v2 2/3] soc: amlogic: gx-socinfo: Add new SoC IDs and Packages IDs Neil Armstrong
2019-03-07 14:01 ` [PATCH v2 3/3] arm64: dts: meson-g12a: Add AO Secure node Neil Armstrong
2019-03-12 20:25 ` Kevin Hilman [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=7hlg1ju9fw.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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;
as well as URLs for NNTP newsgroup(s).