linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: linux@armlinux.org.uk, nicolas.ferre@microchip.com,
	alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
	catalin.marinas@arm.com, will@kernel.org, olivia@selenic.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	vkoul@kernel.org, andi.shyti@kernel.org, broonie@kernel.org,
	gregkh@linuxfoundation.org, jirislaby@kernel.org,
	arnd@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	dmaengine@vger.kernel.org, linux-i2c@vger.kernel.org,
	linux-spi@vger.kernel.org, linux-serial@vger.kernel.org,
	o.rempel@pengutronix.de, daniel.machon@microchip.com,
	Robert Marko <robert.marko@sartura.hr>
Cc: luka.perkov@sartura.hr
Subject: Re: (subset) [PATCH v8 04/10] mfd: at91-usart: Make it selectable for ARCH_MICROCHIP
Date: Thu, 24 Jul 2025 11:04:42 +0100	[thread overview]
Message-ID: <20250724100442.GX11056@google.com> (raw)
In-Reply-To: <175325995961.1695705.8338983998485530536.b4-ty@kernel.org>

On Wed, 23 Jul 2025, Lee Jones wrote:

> On Wed, 02 Jul 2025 20:36:02 +0200, Robert Marko wrote:
> > LAN969x uses the Atmel USART, so make it selectable for ARCH_MICROCHIP to
> > avoid needing to update depends in future if other Microchip SoC-s use it
> > as well.
> > 
> > 
> 
> Applied, thanks!
> 
> [04/10] mfd: at91-usart: Make it selectable for ARCH_MICROCHIP
>         commit: ef37a1e2485724f5287db1584d8aba48e8ba3f41

Reverted as it caused issues in -next.

https://lore.kernel.org/all/20250724115409.030d0d08@canb.auug.org.au/

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-07-24 10:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 18:35 [PATCH v8 00/10] arm64: lan969x: Add support for Microchip LAN969x SoC Robert Marko
2025-07-02 18:35 ` [PATCH v8 01/10] arm64: Add config for Microchip SoC platforms Robert Marko
2025-07-02 19:57   ` Arnd Bergmann
2025-07-03 12:25     ` Robert Marko
2025-07-03 13:55       ` Nicolas Ferre
2025-07-04 17:36         ` Robert Marko
2025-08-11 12:20           ` Daniel Machon
2025-07-03 14:21     ` Conor Dooley
2025-07-02 18:36 ` [PATCH v8 02/10] ARM: at91: select ARCH_MICROCHIP Robert Marko
2025-07-02 18:36 ` [PATCH v8 03/10] arm64: lan969x: Add support for Microchip LAN969x SoC Robert Marko
2025-07-02 18:36 ` [PATCH v8 04/10] mfd: at91-usart: Make it selectable for ARCH_MICROCHIP Robert Marko
2025-07-23  8:39   ` (subset) " Lee Jones
2025-07-24 10:04     ` Lee Jones [this message]
2025-07-27 12:55       ` Robert Marko
2025-07-02 18:36 ` [PATCH v8 05/10] tty: serial: atmel: make " Robert Marko
2025-07-02 18:36 ` [PATCH v8 06/10] spi: " Robert Marko
2025-07-02 18:36 ` [PATCH v8 07/10] i2c: at91: " Robert Marko
2025-07-02 18:36 ` [PATCH v8 08/10] dma: xdmac: " Robert Marko
2025-07-02 18:36 ` [PATCH v8 09/10] char: hw_random: atmel: " Robert Marko
2025-07-02 18:36 ` [PATCH v8 10/10] crypto: atmel-aes: " Robert Marko
2025-07-23 12:29 ` (subset) [PATCH v8 00/10] arm64: lan969x: Add support for Microchip LAN969x SoC Vinod Koul
2025-07-31  8:05   ` Claudiu Beznea
2025-09-03 13:16     ` Alexander Dahl
2025-09-03 14:01       ` Nicolas Ferre

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=20250724100442.GX11056@google.com \
    --to=lee@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andi.shyti@kernel.org \
    --cc=arnd@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=daniel.machon@microchip.com \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luka.perkov@sartura.hr \
    --cc=nicolas.ferre@microchip.com \
    --cc=o.rempel@pengutronix.de \
    --cc=olivia@selenic.com \
    --cc=robert.marko@sartura.hr \
    --cc=vkoul@kernel.org \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).