From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <boris.brezillon@collabora.com>,
Sekhar Nori <nsekhar@ti.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-mtd@lists.infradead.org
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>
Subject: Re: [PATCH v2 2/4] mtd: rawnand: davinci: Stop using nand_chip.legacy.IO_ADDR_{R, W}
Date: Sun, 24 May 2020 21:10:42 +0200 [thread overview]
Message-ID: <20200524191042.25512-1-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20200513172248.141402-2-boris.brezillon@collabora.com>
On Wed, 2020-05-13 at 17:22:46 UTC, Boris Brezillon wrote:
> We can use info->current_cs directly instead of doing this weird
> IO_ADDR_{R,W} re-assignment dance.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
> Tested-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git nand/next, thanks.
Miquel
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-05-24 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 17:22 [PATCH v2 1/4] mtd: rawnand: davinci: Inherit from nand_controller Boris Brezillon
2020-05-13 17:22 ` [PATCH v2 2/4] mtd: rawnand: davinci: Stop using nand_chip.legacy.IO_ADDR_{R, W} Boris Brezillon
2020-05-24 19:10 ` Miquel Raynal [this message]
2020-05-13 17:22 ` [PATCH v2 3/4] mtd: rawnand: davinci: Implement exec_op() Boris Brezillon
2020-05-24 19:10 ` Miquel Raynal
2020-05-13 17:22 ` [PATCH v2 4/4] mtd: rawnand: davinci: Get rid of the legacy interface implementation Boris Brezillon
2020-05-24 19:10 ` Miquel Raynal
2020-05-24 19:10 ` [PATCH v2 1/4] mtd: rawnand: davinci: Inherit from nand_controller Miquel Raynal
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=20200524191042.25512-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=bgolaszewski@baylibre.com \
--cc=boris.brezillon@collabora.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nsekhar@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.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 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.