From: Chen-Yu Tsai <wens@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: Chen-Yu Tsai <wens@csie.org>, Maxime Ripard <mripard@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner Fixes for 5.6 - part 2
Date: Fri, 13 Mar 2020 14:07:27 +0800 [thread overview]
Message-ID: <20200313060727.GA23962@wens.csie.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1848 bytes --]
Hi,
The changes in this pull request are likely a bit contentious, as they
should have been in part of the merge window PRs, so I'm sending these
as a follow-up.
The patches in question were posted on Nov. 20 last year, and the driver
change was merged on Dec. 11, but we failed to merge the DT side of the
series [1]. Here's hoping we can still get those changes in the same
release.
ChenYu
[1] https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=205943
The following changes since commit d9b553b02e691185f8145637c46f9564395936e2:
ARM: dts: sun8i: r40: Move SPI device nodes based on address order (2020-03-11 22:49:40 +0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git sunxi-fixes-for-5.6-2
for you to fetch changes up to 00cef5e404a6c6e72cbec1fd7a41b01890b8d340:
ARM: dts: sun8i: a33: add the new SS compatible (2020-03-11 23:12:06 +0800)
----------------------------------------------------------------
Allwinner Fixes for 5.6 - part 2
This follows up on the previous 5.6 fixes tag with a fix for the A33
Security System (crypto offloading hardware). The hardware was found
to not be compatible with existing hardware and a new compatible was
needed.
The driver change was picked up right before the previous -rc6 and
the DT bindings and DT changes were not picked up. The goal is to have
all the changes in the same release, that is v5.6.
----------------------------------------------------------------
Corentin Labbe (2):
dt-bindings: crypto: add new compatible for A33 SS
ARM: dts: sun8i: a33: add the new SS compatible
.../devicetree/bindings/crypto/allwinner,sun4i-a10-crypto.yaml | 2 ++
arch/arm/boot/dts/sun8i-a33.dtsi | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-03-13 6:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200313060727.GA23962@wens.csie.org \
--to=wens@kernel.org \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=soc@kernel.org \
--cc=wens@csie.org \
/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.