public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: niravkumar.l.rabara@intel.com
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 linux@treblig.org,  Shen Lichuan <shenlichuan@vivo.com>,
	 Jinjie Ruan <ruanjinjie@huawei.com>,
	u.kleine-koenig@baylibre.com,  linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] mtd: rawnand: cadence: improvement and fixes
Date: Wed, 15 Jan 2025 20:05:19 +0100	[thread overview]
Message-ID: <87jzavnbio.fsf@bootlin.com> (raw)
In-Reply-To: <20250108135234.3107502-1-niravkumar.l.rabara@intel.com> (niravkumar l. rabara's message of "Wed, 8 Jan 2025 21:52:31 +0800")

Hello,

On 08/01/2025 at 21:52:31 +08, niravkumar.l.rabara@intel.com wrote:

> From: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
>
> This patchset introduces improvements and fixes for cadence nand driver.
> The changes include:
>
> 1. Support deferred prob mechanism when DMA driver is not probed yet.
> 2. Map the slave DMA address using dma_map_resource. When ARM SMMU
>    is enabled, using a direct physical address of SDMA results in
>    DMA transaction failure.
> 3. Fixed the incorrect device context used for dma_unmap_single.

The patches look good but they all miss the Fixes and Cc: stable tags,
as I believe these fixes should be backported.

Please send an updated version with those.

Thanks,
Miquèl

      parent reply	other threads:[~2025-01-15 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 13:52 [PATCH 0/3] mtd: rawnand: cadence: improvement and fixes niravkumar.l.rabara
2025-01-08 13:52 ` [PATCH 1/3] mtd: rawnand: cadence: support deferred prob when DMA is not ready niravkumar.l.rabara
2025-01-08 13:52 ` [PATCH 2/3] mtd: rawnand: cadence: use dma_map_resource for sdma address niravkumar.l.rabara
2025-01-08 13:52 ` [PATCH 3/3] mtd: rawnand: cadence: fix incorrect dev context in dma_unmap_single niravkumar.l.rabara
2025-01-15 19:05 ` Miquel Raynal [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=87jzavnbio.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@treblig.org \
    --cc=niravkumar.l.rabara@intel.com \
    --cc=richard@nod.at \
    --cc=ruanjinjie@huawei.com \
    --cc=shenlichuan@vivo.com \
    --cc=u.kleine-koenig@baylibre.com \
    --cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox