From: patchwork-bot+linux-amlogic@kernel.org
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH v2] soc: amlogic: meson-gx-socinfo: Fix S905X3 and S905D3 ID's
Date: Tue, 07 Jul 2020 18:51:11 +0000 [thread overview]
Message-ID: <159414787147.3387.754139708922968561.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200609081318.28023-1-christianshewitt@gmail.com>
Hello:
This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Tue, 9 Jun 2020 08:13:18 +0000 you wrote:
> Correct the SoC revision and package bits/mask values for S905D3/X3 to detect
> a wider range of observed SoC IDs, and tweak sort order for A311D/S922X.
>
> S905X3 05 0000 0101 (SEI610 initial devices)
> S905X3 10 0001 0000 (ODROID-C4 and recent Android boxes)
> S905X3 50 0101 0000 (SEI610 later revisions)
> S905D3 04 0000 0100 (VIM3L devices in kernelci)
> S905D3 b0 1011 0000 (VIM3L initial production)
>
> [...]
Here is a summary with links:
- [v2] soc: amlogic: meson-gx-socinfo: Fix S905X3 and S905D3 ID's
https://git.kernel.org/khilman/linux-amlogic/c/d16d0481e6bab5a916450e4ef0e1c958b550880c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-07-07 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 8:13 [PATCH v2] soc: amlogic: meson-gx-socinfo: Fix S905X3 and S905D3 ID's Christian Hewitt
2020-06-09 8:13 ` Christian Hewitt
2020-06-09 8:13 ` Christian Hewitt
2020-06-22 7:58 ` Neil Armstrong
2020-06-29 23:20 ` Kevin Hilman
2020-06-29 23:20 ` Kevin Hilman
2020-06-29 23:20 ` Kevin Hilman
2020-07-07 18:51 ` patchwork-bot+linux-amlogic [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=159414787147.3387.754139708922968561.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=christianshewitt@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.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.