From: Andrew Lunn <andrew@lunn.ch>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>,
linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
dwmw2@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] mtd: mchp23k256: device tree and mchp23lcv1024
Date: Tue, 23 May 2017 13:52:17 +0200 [thread overview]
Message-ID: <20170523115217.GM13759@lunn.ch> (raw)
In-Reply-To: <20170523093957.24110476@bbrezillon>
On Tue, May 23, 2017 at 09:39:57AM +0200, Boris Brezillon wrote:
> On Tue, 23 May 2017 12:43:12 +1200
> Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
>
> > This series adds device tree support to the mchp23k256 driver and
> > support for the mchp23lcv1024 chip. I suspect there are more compatible
> > variants that we could now enumerate if desired.
> >
> > Chris Packham (5):
> > mtd: mchp23k256: Add OF device ID table
> > mtd: mchp23k256: switch to mtd_device_register()
> > mtd: handle partitioning on devices with 0 erasesize
> > mtd: mchp23k256: add partitioning support
> > mtd: mchp23k256: Add support for mchp23lcv1024
>
> Shouldn't we add a spi_device_id table to allow non-DT users to probe
> mchp23lcv1024 chips?
Hi Boris
This is something which can be added at any time. Currently there is
no need for it, so i personally would wait until somebody does need
it.
Andrew
prev parent reply other threads:[~2017-05-23 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 0:43 [PATCH v3 0/5] mtd: mchp23k256: device tree and mchp23lcv1024 Chris Packham
2017-05-23 0:43 ` [PATCH v3 1/5] mtd: mchp23k256: Add OF device ID table Chris Packham
2017-05-23 0:43 ` [PATCH v3 2/5] mtd: mchp23k256: switch to mtd_device_register() Chris Packham
2017-05-23 0:43 ` [PATCH v3 3/5] mtd: handle partitioning on devices with 0 erasesize Chris Packham
2017-05-23 0:43 ` [PATCH v3 4/5] mtd: mchp23k256: add partitioning support Chris Packham
2017-05-23 0:43 ` [PATCH v3 5/5] mtd: mchp23k256: Add support for mchp23lcv1024 Chris Packham
2017-05-23 0:58 ` Andrew Lunn
2017-05-23 1:38 ` Chris Packham
2017-05-23 1:57 ` Andrew Lunn
2017-05-23 7:14 ` Boris Brezillon
2017-05-23 20:29 ` Chris Packham
2017-05-23 7:39 ` [PATCH v3 0/5] mtd: mchp23k256: device tree and mchp23lcv1024 Boris Brezillon
2017-05-23 11:52 ` Andrew Lunn [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=20170523115217.GM13759@lunn.ch \
--to=andrew@lunn.ch \
--cc=boris.brezillon@free-electrons.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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).