From: Alexander Sverdlin <alexander.sverdlin@nokia.com>
To: Tudor.Ambarus@microchip.com
Cc: vigneshr@ti.com, sergei.shtylyov@cogentembedded.com,
richard@nod.at, john.garry@huawei.com, linuxarm@huawei.com,
yangyicong@hisilicon.com, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com
Subject: Re: [PATCH] mtd: spi-nor: sfdp: Fix wrong addr length and dummy when perform SMPT detection command
Date: Tue, 21 Apr 2020 12:39:14 +0200 [thread overview]
Message-ID: <6c3bdfd9-1fd8-6a8e-0e30-03eb82f1f244@nokia.com> (raw)
In-Reply-To: <5032403.BAliFFt8qx@192.168.0.120>
Hi!
On 21/04/2020 11:58, Tudor.Ambarus@microchip.com wrote:
>> Well this will work and as the maintainers ignore the proper and even
>> recommended by them solution,
> There will be no patch left behind or ignored. Your patch is still pending in
> the review state because I need some time to study the problem and I couldn't
> allocate time for this yet. But I will address it in a week or so.
With all the rework of spi-nor it barely makes sense and if I rework the patches
there is no way they can be backported to stable. I wonder why at all subsystem
rework is prioritized over bugfixes in MTD.
--
Best regards,
Alexander Sverdlin.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-04-21 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 3:30 [PATCH] mtd: spi-nor: sfdp: Fix wrong addr length and dummy when perform SMPT detection command Yicong Yang
2020-04-21 7:54 ` Alexander Sverdlin
2020-04-21 9:58 ` Tudor.Ambarus
2020-04-21 10:39 ` Alexander Sverdlin [this message]
2020-04-21 11:14 ` Tudor.Ambarus
2020-04-21 11:44 ` Pratyush Yadav
2020-04-21 12:25 ` Yicong Yang
2020-04-22 13:51 ` Pratyush Yadav
2020-04-23 11:09 ` Yicong Yang
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=6c3bdfd9-1fd8-6a8e-0e30-03eb82f1f244@nokia.com \
--to=alexander.sverdlin@nokia.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=john.garry@huawei.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=vigneshr@ti.com \
--cc=yangyicong@hisilicon.com \
/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