From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, conor.dooley@microchip.com,
daire.mcnamara@microchip.com, jamie.gibbons@microchip.com,
valentina.fernandezalanis@microchip.com,
linus.walleij@linaro.org, brgl@bgdev.pl, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, lpieralisi@kernel.org,
kw@linux.com, bhelgaas@google.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v1 0/5] BeagleV Fire support
Date: Wed, 22 May 2024 23:32:23 +0000 [thread overview]
Message-ID: <171642074357.9409.6131755278467232949.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240327-parkway-dodgy-f0fe1fa20892@spud>
Hello:
This series was applied to riscv/linux.git (fixes)
by Rob Herring (Arm) <robh@kernel.org>:
On Wed, 27 Mar 2024 12:24:35 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Yo,
>
> Wee series adding support for the BeagleV Fire. I've had a dts sitting
> locally for this for over a year for testing Auto Update and I meant to
> submit something to mainline once the board got announced publicly, but
> only got around to that now.
>
> [...]
Here is the summary with links:
- [v1,1/5] dt-bindings: riscv: microchip: document beaglev-fire
(no matching commit)
- [v1,2/5] dt-bindings: gpio: mpfs: add coreGPIO support
https://git.kernel.org/riscv/c/6e12a52c1459
- [v1,3/5] dt-bindings: gpio: mpfs: allow gpio-line-names
https://git.kernel.org/riscv/c/f752a52d34cb
- [v1,4/5] dt-bindings: PCI: microchip: increase number of items in ranges property
https://git.kernel.org/riscv/c/649bad67d4b1
- [v1,5/5] riscv: dts: microchip: add an initial devicetree for the BeagleV Fire
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, conor.dooley@microchip.com,
daire.mcnamara@microchip.com, jamie.gibbons@microchip.com,
valentina.fernandezalanis@microchip.com,
linus.walleij@linaro.org, brgl@bgdev.pl, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, lpieralisi@kernel.org,
kw@linux.com, bhelgaas@google.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v1 0/5] BeagleV Fire support
Date: Wed, 22 May 2024 23:32:23 +0000 [thread overview]
Message-ID: <171642074357.9409.6131755278467232949.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240327-parkway-dodgy-f0fe1fa20892@spud>
Hello:
This series was applied to riscv/linux.git (fixes)
by Rob Herring (Arm) <robh@kernel.org>:
On Wed, 27 Mar 2024 12:24:35 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Yo,
>
> Wee series adding support for the BeagleV Fire. I've had a dts sitting
> locally for this for over a year for testing Auto Update and I meant to
> submit something to mainline once the board got announced publicly, but
> only got around to that now.
>
> [...]
Here is the summary with links:
- [v1,1/5] dt-bindings: riscv: microchip: document beaglev-fire
(no matching commit)
- [v1,2/5] dt-bindings: gpio: mpfs: add coreGPIO support
https://git.kernel.org/riscv/c/6e12a52c1459
- [v1,3/5] dt-bindings: gpio: mpfs: allow gpio-line-names
https://git.kernel.org/riscv/c/f752a52d34cb
- [v1,4/5] dt-bindings: PCI: microchip: increase number of items in ranges property
https://git.kernel.org/riscv/c/649bad67d4b1
- [v1,5/5] riscv: dts: microchip: add an initial devicetree for the BeagleV Fire
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-05-22 23:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 12:24 [PATCH v1 0/5] BeagleV Fire support Conor Dooley
2024-03-27 12:24 ` Conor Dooley
2024-03-27 12:24 ` [PATCH v1 1/5] dt-bindings: riscv: microchip: document beaglev-fire Conor Dooley
2024-03-27 12:24 ` Conor Dooley
2024-03-27 17:56 ` Rob Herring
2024-03-27 17:56 ` Rob Herring
2024-03-27 12:24 ` [PATCH v1 2/5] dt-bindings: gpio: mpfs: add coreGPIO support Conor Dooley
2024-03-27 12:24 ` Conor Dooley
2024-03-27 17:57 ` Rob Herring
2024-03-27 17:57 ` Rob Herring
2024-03-29 10:28 ` Bartosz Golaszewski
2024-03-29 10:28 ` Bartosz Golaszewski
2024-03-27 12:24 ` [PATCH v1 3/5] dt-bindings: gpio: mpfs: allow gpio-line-names Conor Dooley
2024-03-27 12:24 ` Conor Dooley
2024-03-27 17:57 ` Rob Herring
2024-03-27 17:57 ` Rob Herring
2024-03-29 10:29 ` Bartosz Golaszewski
2024-03-29 10:29 ` Bartosz Golaszewski
2024-03-27 12:24 ` [PATCH v1 4/5] dt-bindings: PCI: microchip: increase number of items in ranges property Conor Dooley
2024-03-27 12:24 ` Conor Dooley
2024-03-27 17:57 ` Rob Herring
2024-03-27 17:57 ` Rob Herring
2024-04-19 15:57 ` Conor Dooley
2024-04-19 15:57 ` Conor Dooley
2024-03-27 12:24 ` [PATCH v1 5/5] riscv: dts: microchip: add an initial devicetree for the BeagleV Fire Conor Dooley
2024-03-27 12:24 ` Conor Dooley
2024-05-28 11:57 ` Conor Dooley
2024-05-28 11:57 ` Conor Dooley
2024-05-22 23:32 ` patchwork-bot+linux-riscv [this message]
2024-05-22 23:32 ` [PATCH v1 0/5] BeagleV Fire support patchwork-bot+linux-riscv
2024-06-19 11:24 ` (subset) " Conor Dooley
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=171642074357.9409.6131755278467232949.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jamie.gibbons@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=valentina.fernandezalanis@microchip.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 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.