From: Boris Brezillon <boris.brezillon@collabora.com>
To: <Tudor.Ambarus@microchip.com>
Cc: richard@nod.at, linux-kernel@vger.kernel.org,
frieder.schrempf@kontron.de, marek.vasut@gmail.com,
linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
dwmw2@infradead.org
Subject: Re: [PATCH 1/2] mtd: spi-nor: Add support for EN25Q80A
Date: Thu, 7 Feb 2019 11:48:50 +0100 [thread overview]
Message-ID: <20190207114843.01c431dd@kernel.org> (raw)
In-Reply-To: <5bdbd64f-bacd-8192-b7eb-6ec4c06baec0@microchip.com>
On Thu, 7 Feb 2019 10:16:05 +0000
<Tudor.Ambarus@microchip.com> wrote:
> Hi, Frieder,
>
> On 02/07/2019 12:06 PM, Schrempf Frieder wrote:
> > Hi Tudor,
> >
> > On 03.02.19 14:33, Tudor.Ambarus@microchip.com wrote:
> >> Hi, Frieder,
> >>
> >> On 01/23/2019 09:56 AM, Schrempf Frieder wrote:
> >>> From: Frieder Schrempf <frieder.schrempf@kontron.de>
> >>>
> >>> This adds support for the EON EN25Q80A, a 8Mb SPI NOR chip.
> >> I would suggest to specify who is using this flash and how did you test it. This
> >> way we will not end up with support for flashes that are not actually used.
> > Ok. The flash is used by a board that I plan to upstream. Maybe I should
> > just resubmit this together with the actual board support patches?
No need to wait for the board patches, they'll be applied independently
anyway. Just mention the board you tested it on in the commit message
(even if it's not upstream yet) and we should be good.
Thanks,
Boris
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-02-07 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 7:56 [PATCH 1/2] mtd: spi-nor: Add support for EN25Q80A Schrempf Frieder
2019-01-23 7:56 ` [PATCH 2/2] mtd: spi-nor: Add support for MX25V8035F Schrempf Frieder
2019-02-03 13:54 ` Tudor.Ambarus
2019-02-03 13:33 ` [PATCH 1/2] mtd: spi-nor: Add support for EN25Q80A Tudor.Ambarus
2019-02-07 10:06 ` Schrempf Frieder
2019-02-07 10:16 ` Tudor.Ambarus
2019-02-07 10:48 ` Boris Brezillon [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=20190207114843.01c431dd@kernel.org \
--to=boris.brezillon@collabora.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=frieder.schrempf@kontron.de \
--cc=linux-kernel@vger.kernel.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).