mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: sashiko-bot@kernel.org
Cc: "Michael Walle" <mwalle@kernel.org>,
	 "Takahiro Kuwano" <takahiro.kuwano@infineon.com>,
	 "Pratyush Yadav" <pratyush@kernel.org>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	 "Richard Weinberger" <richard@nod.at>,
	 haibo.chen@oss.nxp.com, sashiko-reviews@lists.linux.dev,
	 linux-mtd@lists.infradead.org, michael@walle.cc,
	 linux-kernel@vger.kernel.org,  "Haibo Chen" <haibo.chen@nxp.com>
Subject: Re: [PATCH v2] mtd: spi-nor: clear the default RDCR opcode when entering Octal DTR
Date: Tue, 29 Sep 2026 09:28:10 +0200	[thread overview]
Message-ID: <87bj9g7bzp.fsf@bootlin.com> (raw)
In-Reply-To: <20260929065924.C12141F00898@smtp.kernel.org> (sashiko-bot@kernel.org's message of "Tue, 29 Sep 2026 06:59:24 +0000")

On 29/09/2026 at 06:59:24 GMT, sashiko-bot@kernel.org wrote:

> Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
> - [High] mtd: spi-nor: compilation error accessing non-existent opcodes.read_sr2
> - [High] mtd: spi-nor: modifying hallucinated opcode does not skip SR2 reads
> - [Medium] mtd: spi-nor: permanent breakage of SR2 reads due to
> missing state restore

Please ignore these. Sashiko did not apply the patch to the correct tree
(-rcX instead of -next).

  reply	other threads:[~2026-09-29  7:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29  6:53 haibo.chen
2026-09-29  6:59 ` sashiko-bot
2026-09-29  7:28   ` Miquel Raynal [this message]
2026-09-29  8:23 ` Miquel Raynal
2026-09-29  9:10   ` Bough Chen (OSS)
2026-09-29 14:02   ` Michael Walle

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=87bj9g7bzp.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=haibo.chen@nxp.com \
    --cc=haibo.chen@oss.nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=mwalle@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=takahiro.kuwano@infineon.com \
    --cc=vigneshr@ti.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

all inboxes | Powered by JetHome®