public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux OpenRISC <linux-openrisc@vger.kernel.org>
Subject: Re: (subset) [PATCH v2 0/5] OpenRISC de0 nano single and multicore boards
Date: Sun, 11 Jan 2026 16:39:22 +0000	[thread overview]
Message-ID: <aWPSOmKD9_bePghi@antec> (raw)
In-Reply-To: <176606559331.6520.4498279930581822500.b4-ty@oss.qualcomm.com>

On Thu, Dec 18, 2025 at 02:46:48PM +0100, Bartosz Golaszewski wrote:
> 
> On Wed, 17 Dec 2025 08:08:26 +0000, Stafford Horne wrote:
> > Since v1:
> >  - Use proper schema in gpio-mmio suggsted by Conor Dooley
> >  - Remove 0 clock-frequency definitions in dtsi file
> > 
> > The patches add support for OpenRISC systems running on the De0 Nano FPGA
> > development board.  We have two SoCs which are available here:
> > 
> > [...]
> 
> Tweaked the commit message a bit and applied, thanks!
> 
> [1/5] dt-bindings: Add compatible string opencores,gpio to gpio-mmio
>       commit: f48b5e8bc2e1344f588cc730082aed6ccc5a6b3e

Hi Bartosz,

After discussion [1] with Linus W and Geert U on this patch we agreed it would be
best to drop this old patch and replace with a patch to add "opencores,gpio" to
the binding and the driver.

I have sent two new patches for that.  Can you please consider dropping this
original patch from your queue and replacing with the new?

If you prefer me to post these in a different way I can do that too.

[1] https://lore.kernel.org/lkml/CAD++jLm1u9ChqsftwvbOptiG3Qo2KWxPjqN2snOVuZDYuVST5Q@mail.gmail.com/

-Stafford

      reply	other threads:[~2026-01-11 16:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17  8:08 [PATCH v2 0/5] OpenRISC de0 nano single and multicore boards Stafford Horne
2025-12-17  8:08 ` [PATCH v2 1/5] dt-bindings: Add compatible string opencores,gpio to gpio-mmio Stafford Horne
2025-12-18  0:55   ` Conor Dooley
2026-01-03  5:55     ` Stafford Horne
2026-01-07 14:17   ` Linus Walleij
2026-01-07 14:35   ` Geert Uytterhoeven
2026-01-08  8:20     ` Stafford Horne
2026-01-08  8:41       ` Geert Uytterhoeven
2026-01-09 10:07         ` Linus Walleij
2026-01-09 10:19           ` Geert Uytterhoeven
2026-01-09 12:51           ` Stafford Horne
2026-01-12  9:25             ` Bartosz Golaszewski
2026-01-13 16:17               ` Stafford Horne
2025-12-17  8:08 ` [PATCH v2 2/5] openrisc: dts: Add de0 nano config and devicetree Stafford Horne
2025-12-18 18:36   ` Geert Uytterhoeven
2026-01-03  6:16     ` Stafford Horne
2026-01-05 11:02       ` Geert Uytterhoeven
2026-01-06  9:54         ` Stafford Horne
2026-01-06 10:18           ` Geert Uytterhoeven
2026-01-08  7:50             ` Stafford Horne
2025-12-17  8:08 ` [PATCH v2 3/5] openrisc: Fix IPIs on simple multicore systems Stafford Horne
2025-12-17  8:08 ` [PATCH v2 4/5] openrisc: dts: Split simple smp dts to dts and dtsi Stafford Horne
2025-12-18 18:37   ` Geert Uytterhoeven
2026-01-03  6:13     ` Stafford Horne
2025-12-17  8:08 ` [PATCH v2 5/5] openrisc: dts: Add de0 nano multicore config and devicetree Stafford Horne
2025-12-18 13:46 ` (subset) [PATCH v2 0/5] OpenRISC de0 nano single and multicore boards Bartosz Golaszewski
2026-01-11 16:39   ` Stafford Horne [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=aWPSOmKD9_bePghi@antec \
    --to=shorne@gmail.com \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-openrisc@vger.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