public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <frieder.schrempf@kontron.de>, <marek.vasut@gmail.com>
Cc: <bbrezillon@kernel.org>, <richard@nod.at>,
	<linux-kernel@vger.kernel.org>, <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 10:16:05 +0000	[thread overview]
Message-ID: <5bdbd64f-bacd-8192-b7eb-6ec4c06baec0@microchip.com> (raw)
In-Reply-To: <52338dfe-aca1-503d-6871-c4be09f1f3ac@kontron.de>

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?
> 
> Likewise for my other patch (MX25V8035F), this is for another board I 
> plan to upstream soon.
> 

Sounds good.

Cheers,
ta

  reply	other threads:[~2019-02-07 10:16 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 [this message]
2019-02-07 10:48       ` 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=5bdbd64f-bacd-8192-b7eb-6ec4c06baec0@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=bbrezillon@kernel.org \
    --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