From: Boris Brezillon <boris.brezillon@bootlin.com>
To: <Tudor.Ambarus@microchip.com>
Cc: <marek.vasut@gmail.com>, <alexandre.belloni@bootlin.com>,
<dwmw2@infradead.org>, <computersforpeace@gmail.com>,
<richard@nod.at>, <linux-mtd@lists.infradead.org>,
<alexander.sverdlin@nokia.com>
Subject: Re: [PATCH v4 2/3] mtd: spi-nor: Add a post BFPT parsing fixup hook
Date: Thu, 6 Dec 2018 11:25:02 +0100 [thread overview]
Message-ID: <20181206112502.3b32bf12@bbrezillon> (raw)
In-Reply-To: <6d2f2c1d-9c95-296e-6907-a8aa8b7b80ef@microchip.com>
On Wed, 5 Dec 2018 16:35:15 +0000
<Tudor.Ambarus@microchip.com> wrote:
> On 11/29/2018 04:41 PM, Boris Brezillon wrote:
> > +struct spi_nor_fixups {
> > + int (*post_bfpt)(struct spi_nor *nor,
> > + const struct sfdp_parameter_header *bfpt_header,
> > + const struct sfdp_bfpt *bfpt,
> > + struct spi_nor_flash_parameter *params);
> > +};
>
> I like the idea. The code looks good. What I noticed is that the sfdp logic is
> now split in different sections of spi-nor file. In order to avoid the burden of
> moving the sfdp code inside spi-nor, you can have these 3 forward declarations
> and do the sfdp move later on, in a separate file.
I tried that, but then I need some of those definitions in my
mx25l25635_post_bfpt_fixups(), so I'm screwed anyway. Also, it's not
really a matter to have SFDP split in 2 sections as we're going to move
all the code in a separate file soon ;-).
next prev parent reply other threads:[~2018-12-06 10:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 14:41 [PATCH v4 0/3] mtd: spi-nor: mx25l25635f: Use 4B opcodes Boris Brezillon
2018-11-29 14:41 ` [PATCH v4 1/3] mtd: spi-nor: Add the SNOR_F_4B_OPCODES flag Boris Brezillon
2018-12-05 15:08 ` Tudor.Ambarus
2018-12-05 15:19 ` Boris Brezillon
2018-12-05 15:48 ` Tudor.Ambarus
2018-12-05 16:00 ` Boris Brezillon
2018-12-05 16:26 ` Tudor.Ambarus
2018-12-05 16:32 ` Boris Brezillon
2018-12-05 16:54 ` Boris Brezillon
2018-11-29 14:41 ` [PATCH v4 2/3] mtd: spi-nor: Add a post BFPT parsing fixup hook Boris Brezillon
2018-12-05 16:35 ` Tudor.Ambarus
2018-12-05 16:47 ` Boris Brezillon
2018-12-06 10:25 ` Boris Brezillon [this message]
2018-11-29 14:41 ` [PATCH v4 3/3] mtd: spi-nor: Add a post BFPT fixup for MX25L25635E Boris Brezillon
2018-12-05 16:41 ` Tudor.Ambarus
2018-12-05 16:50 ` 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=20181206112502.3b32bf12@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=alexander.sverdlin@nokia.com \
--cc=alexandre.belloni@bootlin.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;
as well as URLs for NNTP newsgroup(s).