From: Boris Brezillon <boris.brezillon@bootlin.com>
To: <Tudor.Ambarus@microchip.com>
Cc: <marek.vasut@gmail.com>, <computersforpeace@gmail.com>,
<dwmw2@infradead.org>, <linux-mtd@lists.infradead.org>,
<richard@nod.at>
Subject: Re: [PATCH v3 3/5] mtd: spi-nor: Stop passing flash_info around
Date: Thu, 6 Dec 2018 14:18:50 +0100 [thread overview]
Message-ID: <20181206141850.6627a2c1@bbrezillon> (raw)
In-Reply-To: <200af4c9-f0bf-30ff-08ca-2679bb07d572@microchip.com>
On Thu, 6 Dec 2018 11:20:49 +0000
<Tudor.Ambarus@microchip.com> wrote:
> On 12/06/2018 12:41 PM, Boris Brezillon wrote:
> > Some functions called from spi_nor_scan() need a flash_info object.
> > Let's assign nor->info early on to avoid passing info as an extra
> > argument to each of these sub-functions.
> >
> > We also stop passing a flash_info object to set_4byte() and use
> > nor->info directly.
>
> Should I apply this on top of git://git.infradead.org/linux-mtd.git spi-nor/next
> branch?
>
> Applying: mtd: spi-nor: Stop passing flash_info around
> error: patch failed: drivers/mtd/spi-nor/spi-nor.c:3659
> error: drivers/mtd/spi-nor/spi-nor.c: patch does not apply
Oops. I forgot to mention that this series now depends on [1] (I
re-ordered patches to get [1] merged as soon as possible).
[1]http://patchwork.ozlabs.org/project/linux-mtd/list/?series=80112
next prev parent reply other threads:[~2018-12-06 13:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 10:41 [PATCH v3 0/5] mtd: spi-nor: Random cleanups Boris Brezillon
2018-12-06 10:41 ` [PATCH v3 1/5] mtd: spi-nor: Drop inline on all internal helpers Boris Brezillon
2018-12-07 9:10 ` [v3,1/5] " Boris Brezillon
2018-12-06 10:41 ` [PATCH v3 2/5] mtd: spi-nor: Avoid forward declaration of internal functions Boris Brezillon
2018-12-06 11:17 ` Tudor.Ambarus
2018-12-07 9:10 ` [v3, " Boris Brezillon
2018-12-06 10:41 ` [PATCH v3 3/5] mtd: spi-nor: Stop passing flash_info around Boris Brezillon
2018-12-06 11:20 ` Tudor.Ambarus
2018-12-06 13:18 ` Boris Brezillon [this message]
2018-12-06 13:35 ` Tudor.Ambarus
2018-12-07 9:10 ` [v3,3/5] " Boris Brezillon
2018-12-06 10:41 ` [PATCH v3 4/5] mtd: spi-nor: Make the enable argument passed to set_byte() a bool Boris Brezillon
2018-12-07 9:10 ` [v3, " Boris Brezillon
2018-12-06 10:41 ` [PATCH v3 5/5] mtd: spi-nor: Add an SPDX tag to spi-nor.{c,h} Boris Brezillon
2018-12-06 11:27 ` Tudor.Ambarus
2018-12-07 9:10 ` [v3,5/5] " Boris Brezillon
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=20181206141850.6627a2c1@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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