Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Daniel Palmer <daniel@0x0f.com>
Cc: soc@kernel.org
Subject: Re: [PATCH 0/3] ARM: mstar: Add initial support for M5Stack UnitV2
Date: Mon, 19 Apr 2021 15:10:09 +0000	[thread overview]
Message-ID: <161884500912.21313.417382182251384944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210417011015.2105280-1-daniel@0x0f.com>

Hello:

This series was applied to soc/soc.git (refs/heads/for-next):

On Sat, 17 Apr 2021 10:10:12 +0900 you wrote:
> This series adds basic support for the soon to be released M5Stack
> UnitV2 based on the SigmaStar SSD202D.
> 
> With the rest of the commits in my tree the SPI NAND, ethernet, USB etc
> should work so the UnitV2 should be fully usable with a mainline-ish
> kernel.
> 
> [...]

Here is the summary with links:
  - [1/3] dt-bindings: vendor-prefixes: Add vendor prefix for M5Stack
    https://git.kernel.org/soc/soc/c/f8d6fb74bbb7
  - [2/3] dt-bindings: arm: mstar: Add compatible for M5Stack UnitV2
    https://git.kernel.org/soc/soc/c/c5208ff7f6c2
  - [3/3] ARM: dts: mstar: Add a dts for M5Stack UnitV2
    https://git.kernel.org/soc/soc/c/3060a15ccaed

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-04-19 15:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-17  1:10 [PATCH 0/3] ARM: mstar: Add initial support for M5Stack UnitV2 Daniel Palmer
2021-04-17  1:10 ` Daniel Palmer
2021-04-17  1:10 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add vendor prefix for M5Stack Daniel Palmer
2021-04-17  1:10   ` Daniel Palmer
2021-04-17  1:10 ` [PATCH 2/3] dt-bindings: arm: mstar: Add compatible for M5Stack UnitV2 Daniel Palmer
2021-04-17  1:10   ` Daniel Palmer
2021-04-17  1:10 ` [PATCH 3/3] ARM: dts: mstar: Add a dts " Daniel Palmer
2021-04-17  1:10   ` Daniel Palmer
2021-04-19 15:10 ` patchwork-bot+linux-soc [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=161884500912.21313.417382182251384944.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=daniel@0x0f.com \
    --cc=soc@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox