All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Jon Lin <jon.lin@rock-chips.com>
Cc: Bin Meng <bmeng.cn@gmail.com>,
	u-boot@lists.denx.de, xxm@rock-chips.com,
	Lin Shawn <shawn.lin@rock-chips.com>,
	zyf@rock-chips.com, Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH v3 1/2] nvme: Enable FUA
Date: Thu, 18 Nov 2021 14:14:49 -0500	[thread overview]
Message-ID: <20211118191449.GI24579@bill-the-cat> (raw)
In-Reply-To: <20211019104049.v3.1.Ic581ec99f46b6dfa2e0b1922e670a333ac859e82@changeid>

[-- Attachment #1: Type: text/plain, Size: 436 bytes --]

On Tue, Oct 19, 2021 at 10:40:53AM +0800, Jon Lin wrote:

> Most NVME devcies maintain data in internal cache for an uncertain
> times, and u-boot has no method to force NVME to flush cache.
> So this patch adds FUA to avoid data loss caused by power off after data
> programming.
> 
> Signed-off-by: Jon Lin <jon.lin@rock-chips.com>
> Reviewed-by: Stefan Agner <stefan@agner.ch>

Applied to u-boot/next, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2021-11-18 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  2:40 [PATCH v3 1/2] nvme: Enable FUA Jon Lin
2021-10-19  2:40 ` [PATCH v3 2/2] nvme: Fix error in nvme_setup_prps Jon Lin
2021-11-18 19:14   ` Tom Rini
2021-10-27 11:51 ` [PATCH v3 1/2] nvme: Enable FUA Bin Meng
2021-11-18 19:14 ` Tom Rini [this message]
2021-11-19  0:56   ` Bin Meng
2021-11-19  1:14     ` Tom Rini
2021-11-22  1:41       ` Jon Lin

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=20211118191449.GI24579@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=bmeng.cn@gmail.com \
    --cc=jon.lin@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=u-boot@lists.denx.de \
    --cc=xxm@rock-chips.com \
    --cc=zyf@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.