Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: soc@kernel.org
Subject: Re: [PATCH v1 0/4] Route RISC-V SoC drivers/firmware/DT via the soc tree
Date: Mon, 14 Nov 2022 13:00:16 +0000	[thread overview]
Message-ID: <166843081635.22003.16583813044179917807.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221109212219.1598355-1-conor@kernel.org>

Hello:

This series was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann <arnd@arndb.de>:

On Wed,  9 Nov 2022 21:22:16 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> Spoke to Palmer today at the linux-riscv pw sync-up (see [0] for anyone
> that may see this and is interested), and he said go for it w/
> MAINTAINERS changes. Routing patches this way was proposed by Palmer @
> [1] where Arnd & I had a wee bit of back and forth about the maintainers
> entries required.
> 
> [...]

Here is the summary with links:
  - [v1,1/4] MAINTAINERS: add entries for misc. RISC-V SoC drivers and devicetrees
    (no matching commit)
  - [v1,2/4] MAINTAINERS: generify the Microchip RISC-V entry name
    https://git.kernel.org/soc/soc/c/d10728ff93b5
  - [v1,3/4] MAINTAINERS: add an entry for StarFive devicetrees
    https://git.kernel.org/soc/soc/c/94803f9e1623
  - [v1,4/4] MAINTAINERS: repair Microchip corei2c driver entry
    https://git.kernel.org/soc/soc/c/d7f6fc14e513

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



      parent reply	other threads:[~2022-11-14 13:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 21:22 [PATCH v1 0/4] Route RISC-V SoC drivers/firmware/DT via the soc tree Conor Dooley
2022-11-09 21:22 ` [PATCH v1 1/4] MAINTAINERS: add entries for misc. RISC-V SoC drivers and devicetrees Conor Dooley
2022-11-14  8:59   ` Nicolas Ferre
2022-11-14 19:44   ` Palmer Dabbelt
2022-11-09 21:22 ` [PATCH v1 2/4] MAINTAINERS: generify the Microchip RISC-V entry name Conor Dooley
2022-11-09 21:22 ` [PATCH v1 3/4] MAINTAINERS: add an entry for StarFive devicetrees Conor Dooley
2022-11-10  8:48   ` Emil Renner Berthing
2022-11-09 21:22 ` [PATCH v1 4/4] MAINTAINERS: repair Microchip corei2c driver entry Conor Dooley
2022-11-14 13:00 ` 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=166843081635.22003.16583813044179917807.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=conor@kernel.org \
    --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