u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: chao zeng <chaochao2021666@163.com>
Cc: U-Boot-Denx <u-boot@lists.denx.de>, Vignesh R <vigneshr@ti.com>,
	 Chao Zeng <chao.zeng@siemens.com>
Subject: Re: [PATCH] sf: Querying write-protect status before operating the flash
Date: Tue, 29 Jun 2021 19:20:28 +0530	[thread overview]
Message-ID: <CAMty3ZA=CTXE1WmDkL=c=ugA2z+kLwvnKiv+SNq_ytytL+UTcA@mail.gmail.com> (raw)
In-Reply-To: <20210622052126.49853-1-chaochao2021666@163.com>

On Tue, Jun 22, 2021 at 10:51 AM chao zeng <chaochao2021666@163.com> wrote:
>
> From: Chao Zeng <chao.zeng@siemens.com>
>
> When operating the write-protection flash,spi_flash_std_write() and
> spi_flash_std_erase() would return wrong result.The flash is protected,
> but write or erase the flash would show "OK".
>
> Check the flash write protection state if the write-protection has enbale
> before operating the flash.
>
> Signed-off-by: Chao Zeng <chao.zeng@siemens.com>
> ---

Does it broken on master? if yes can you check in u-boot-spi/next?

Jagan.

  reply	other threads:[~2021-06-29 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  5:21 [PATCH] sf: Querying write-protect status before operating the flash chao zeng
2021-06-29 13:50 ` Jagan Teki [this message]
2021-09-08  4:55   ` chaochao2021666
2021-09-13  7:48     ` Jan Kiszka
2021-10-04 13:36       ` Jan Kiszka
2021-11-03 12:18         ` Jan Kiszka
2021-11-04 16:06           ` Tom Rini
2021-11-05 17:17 ` Tudor.Ambarus
2021-11-05 18:08   ` Jagan Teki
2021-11-08  9:50     ` [PATCH] sf: Querying write-protect status before operating the Michael Walle
2021-11-08 11:01       ` Tudor.Ambarus
2021-11-09  1:52     ` Re:Re: [PATCH] sf: Querying write-protect status before operating the flash chaochao2021666
2021-11-09  8:14       ` Tudor.Ambarus

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='CAMty3ZA=CTXE1WmDkL=c=ugA2z+kLwvnKiv+SNq_ytytL+UTcA@mail.gmail.com' \
    --to=jagan@amarulasolutions.com \
    --cc=chao.zeng@siemens.com \
    --cc=chaochao2021666@163.com \
    --cc=u-boot@lists.denx.de \
    --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;
as well as URLs for NNTP newsgroup(s).