[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YwN1s4bEKP2jX8Qm@sirena.org.uk>
Date: Mon, 22 Aug 2022 13:25:23 +0100
From: Mark Brown <broonie@...nel.org>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Brad Larson <brad@...sando.io>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org, adrian.hunter@...el.com,
alcooperx@...il.com, andy.shevchenko@...il.com, arnd@...db.de,
blarson@....com, brijeshkumar.singh@....com,
catalin.marinas@....com, gsomlo@...il.com, gerg@...ux-m68k.org,
krzk@...nel.org, krzysztof.kozlowski+dt@...aro.org,
lee.jones@...aro.org, yamada.masahiro@...ionext.com,
p.zabel@...gutronix.de, piotrs@...ence.com, p.yadav@...com,
rdunlap@...radead.org, robh+dt@...nel.org, samuel@...lland.org,
fancer.lancer@...il.com, suravee.suthikulpanit@....com,
thomas.lendacky@....com, will@...nel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v6 17/17] mmc: sdhci-cadence: Support mmc hardware reset
On Mon, Aug 22, 2022 at 12:53:22PM +0200, Ulf Hansson wrote:
> Other than the comments above, I wonder about what merging strategy we
> should use for the series. I believe it looks fine for me to pick up
> the mmc related patches, thus we can apply patches on a per subsystem
> basis, right?
Yes, if there's no relationship between the different subsystem
components (which looks like the case?) they should probably just go
separately - they can probably be submitted separately too.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists