U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: dmukhin@ford.com
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: dmukhin@ford.com, u-boot@lists.denx.de, sjg@chromium.org,
	trini@konsulko.com
Subject: Re: [PATCH v1 3/5] cmd: nvme: Add flush support
Date: Thu, 28 May 2026 20:36:36 -0700	[thread overview]
Message-ID: <ahkJxPyWARHRloQ5@kraken> (raw)
In-Reply-To: <93b97c39-b3c8-4ec4-83f0-af1ca93fceec@linaro.org>

On Thu, May 28, 2026 at 11:29:51AM +0200, Neil Armstrong wrote:
> On 5/28/26 03:20, dmukhin@ford.com wrote:
> > From: Denis Mukhin <dmukhin@ford.com>
> > 
> > Introduce `nvme flush` to allow users to commit all dirty data explicitly
> > to the current NVMe device.
> 
> This adds flush for all blk devices, please rewrite
> the commit subject, message and update all blk commands
> and not only nvme.

Will update, thanks!

--
Denis

  reply	other threads:[~2026-05-29  3:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  1:20 [PATCH v1 0/5] nvme: few fixups dmukhin
2026-05-28  1:20 ` [PATCH v1 1/5] drivers: nvme: Log I/O timeouts dmukhin
2026-05-28  9:11   ` Neil Armstrong
2026-05-29  3:25     ` dmukhin
2026-05-28  1:20 ` [PATCH v1 2/5] drivers: nvme: Implement NVMe flush command (0x0) dmukhin
2026-05-28  9:28   ` Neil Armstrong
2026-05-29  3:36     ` dmukhin
2026-05-29  7:54       ` Neil Armstrong
2026-06-05  3:43         ` dmukhin
2026-06-05  8:01           ` Neil Armstrong
2026-05-28  1:20 ` [PATCH v1 3/5] cmd: nvme: Add flush support dmukhin
2026-05-28  9:29   ` Neil Armstrong
2026-05-29  3:36     ` dmukhin [this message]
2026-05-28  1:20 ` [PATCH v1 4/5] drivers: nvme: Export nvme_shutdown symbol dmukhin
2026-05-28  1:20 ` [PATCH v1 5/5] docs: nvme: Update QEMU command for testing dmukhin

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=ahkJxPyWARHRloQ5@kraken \
    --to=dmukhin@ford.com \
    --cc=neil.armstrong@linaro.org \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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