From: <Tudor.Ambarus@microchip.com>
To: <alexander.sverdlin@nokia.com>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd: spi-nor: fix erase_type array to indicate current map conf
Date: Thu, 22 Nov 2018 15:01:19 +0000 [thread overview]
Message-ID: <a8f305c1-ed85-e9c7-1c9d-c60adb74969e@microchip.com> (raw)
In-Reply-To: <70de11e0-0f49-19e4-b6c7-9177c4fd760a@nokia.com>
Hi, Alexander,
On 11/22/2018 04:56 PM, Sverdlin, Alexander (Nokia - DE/Ulm) wrote:
> Hello Tudor,
>
> On 22/11/2018 13:38, Tudor.Ambarus@microchip.com wrote:
>> Can you please test this patch to see if it fixes your problem?
>
> the patch applies neither to Linus's master nor to spi-nor/next (of l2-mtd tree) branches.
> What have you used as a base for your patch?
http://git.infradead.org/linux-mtd.git, mtd/fixes branch
>
>> On 11/22/2018 02:36 PM, Tudor Ambarus - M18064 wrote:
>>> From: Tudor Ambarus <tudor.ambarus@microchip.com>
>>>
>>> Bug reported for the out-of-tree S25FS128S flash memory.
>
> It turned out to be not relevant, S25FS128S works with upstream Linux as well, just
> the entry is named s25fl129p1...
ok, will remove this comment if so.
Cheers,
ta
next prev parent reply other threads:[~2018-11-22 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 12:36 [PATCH] mtd: spi-nor: fix erase_type array to indicate current map conf Tudor.Ambarus
2018-11-22 12:38 ` Tudor.Ambarus
2018-11-22 14:56 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2018-11-22 15:01 ` Tudor.Ambarus [this message]
2018-11-22 16:14 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2018-11-22 16:22 ` Tudor.Ambarus
2018-11-23 9:42 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2018-11-23 10:17 ` Boris Brezillon
2018-11-23 10:29 ` Boris Brezillon
2018-11-23 10:32 ` Tudor.Ambarus
2018-11-23 11:33 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2018-11-23 12:39 ` Tudor.Ambarus
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=a8f305c1-ed85-e9c7-1c9d-c60adb74969e@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=alexander.sverdlin@nokia.com \
--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