From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "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: Fri, 30 Oct 2020 18:39:35 +0000 [thread overview]
Message-ID: <aefef0187e5ebbe315e57e834ff1ba756ba88817.camel@infinera.com> (raw)
In-Reply-To: <20201030184736.4ec434f5@xps13>
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 ?
>
> 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.
Jocke
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-10-30 18:40 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 [this message]
2020-10-30 18:52 ` Miquel Raynal
2020-10-31 11:26 ` Joakim Tjernlund
2020-11-04 5:42 ` Vignesh Raghavendra
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=aefef0187e5ebbe315e57e834ff1ba756ba88817.camel@infinera.com \
--to=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