Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
	"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] mtd: cfi_cmdset_0002: Use status register where possible
Date: Wed, 4 Nov 2020 11:12:09 +0530	[thread overview]
Message-ID: <31ce9a84-d949-c1d1-a8c6-44ead119ca1b@ti.com> (raw)
In-Reply-To: <931f422255204f0420e6f1b79657f9770ce0cf6e.camel@infinera.com>

Hi Joakim

On 10/31/20 4:56 PM, Joakim Tjernlund wrote:
> On Fri, 2020-10-30 at 19:52 +0100, Miquel Raynal wrote:
>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>
>>
>> Hi Joakim,
>>
>> Joakim Tjernlund <Joakim.Tjernlund@infinera.com> wrote on Fri, 30 Oct
>> 2020 18:39:35 +0000:
>>
>>> On Fri, 2020-10-30 at 18:47 +0100, Miquel Raynal wrote:
>>>>
>>>> Hi Joakim,
>>>
>>> Hi Miquel
>>>
>>>>
>>>> Please Cc the MTD maintainers, not only the list (get_maintainers.pl).
>>>
>>> I figure all maintainers are on the list ?
>>
>> I personally don't look at the list very often. I expect patches to be
>> directed to me (in the current case, Vignesh) when I am concerned.
> 
> Added Vignesh
> 

As Miquel suggested, I look at patches on mailing list at a lower
priority than patches that are CC'd to me.


>>
>>>
>>>>
>>>> Joakim Tjernlund <joakim.tjernlund@infinera.com> wrote on Thu, 22 Oct
>>>> 2020 17:45:06 +0200:
>>>>
>>>>> Commit "mtd: cfi_cmdset_0002: Add support for polling status register"
>>>>> added support for polling the status rather than using DQ polling.
>>>>> However, status register is used only when DQ polling is missing.
>>>>> Lets use status register when available as it is superior to DQ polling.
>>>>>
>>>>
>>>> I will let vignesh comment about the content (looks fine by me) but you will
>>>> need a Fixes tag here.
>>>
>>> This is not a Fixes situation, no bug just a hw enabling thing.
>>> Also, I would like to see the Status patches be backported to 4.19 as well.
>>
>> Backporting features is IMHO not relevant. I guess stable kernel only
>> take fixes...
> 
> This is not a feature really and the 5.4 stable did get them, I ask 4.19 get them too.
> 

commit 4844ef80305d ("mtd: cfi_cmdset_0002: Add support for polling
status register") was added in 5.3 and therefore is part of 5.4. But
note that this is a "new feature" and therefore won't be backported to
kernels older than 5.3.

Similarly, this patch (when accepted) is not a candidate for stable
kernel backports because the intention of enabling polling status
register for Write Completion is to enable flashes that "don't" support
DQ polling at all (mainly HyperFlash).
Enabling this for all flashes that support the feature is not a bug fix
IMO. Also, there isn't enough testing to prove that feature works for
all CFI NOR flashes on all platforms and therefore would be risky to be
backported to stable kernels.

Regards
Vignehs


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-11-04  5:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 15:45 [PATCH] mtd: cfi_cmdset_0002: Use status register where possible Joakim Tjernlund
2020-10-30 17:47 ` Miquel Raynal
2020-10-30 18:39   ` Joakim Tjernlund
2020-10-30 18:52     ` Miquel Raynal
2020-10-31 11:26       ` Joakim Tjernlund
2020-11-04  5:42         ` Vignesh Raghavendra [this message]
2020-11-04  9:53           ` Joakim Tjernlund
2020-11-05 16:04             ` Vignesh Raghavendra
2020-11-05 16:44               ` Joakim Tjernlund
2020-11-05 15:57 ` Vignesh Raghavendra

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=31ce9a84-d949-c1d1-a8c6-44ead119ca1b@ti.com \
    --to=vigneshr@ti.com \
    --cc=Joakim.Tjernlund@infinera.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=stable@vger.kernel.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