From: Thorsten Leemhuis <email@example.com> To: Tokunori Ikegami <firstname.lastname@example.org>, email@example.com Cc: firstname.lastname@example.org, Ahmad Fatoum <email@example.com>, firstname.lastname@example.org Subject: Re: [PATCH] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N Date: Fri, 4 Mar 2022 08:06:53 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi, this is your Linux kernel regression tracker. On 14.02.22 19:20, Tokunori Ikegami wrote: > The regression issue has been caused on S29GL064N and reported it. > Also the change mentioned is to use chip_good() for buffered write. > So disable the change on S29GL064N and use chip_ready() as before. > > Fixes: dfeae1073583("mtd: cfi_cmdset_0002: Change write buffer to check correct value") > Signed-off-by: Tokunori Ikegami <email@example.com> > Tested-by: Ahmad Fatoum <firstname.lastname@example.org> > Cc: email@example.com > Cc: firstname.lastname@example.org This is missing a "Link:" tag pointing to the report: Link: https://email@example.com/ 'Documentation/process/submitting-patches.rst' and 'Documentation/process/5.Posting.rst' explain this in more detail. Such tags are important for me, as it allows my regression tracking bot to connect the report with any patches posted or committed to fix the issue; this again allows the bot to show the current status of regressions and automatically resolve the issue when the fix hits the right tree. BTW, what's the status of getting an improved fix merged? It seems the progress slowed down quite a bit. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them and lack knowledge about most of the areas they concern. I thus unfortunately will sometimes get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight. #regzbot ^backmonitor: https://firstname.lastname@example.org/
prev parent reply other threads:[~2022-03-04 7:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-14 18:20 Tokunori Ikegami 2022-02-15 9:05 ` Ahmad Fatoum 2022-02-28 15:34 ` Vignesh Raghavendra 2022-03-06 15:40 ` Tokunori Ikegami 2022-03-04 7:06 ` Thorsten Leemhuis [this message]
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).