From: dmukhin@ford.com
To: Simon Glass <sjg@chromium.org>
Cc: dmukhin@ford.com, u-boot@lists.denx.de,
neil.armstrong@linaro.org, trini@konsulko.com
Subject: Re: [PATCH v2 2/6] drivers: block: Introduce blk_flush()/blk_dflush()
Date: Thu, 16 Jul 2026 15:28:01 -0700 [thread overview]
Message-ID: <alla8U6P8/VE8tsG@kraken> (raw)
In-Reply-To: <CAFLszTgz6ia9qgkSq=2=JT+csdo=9O8KpjJeYi1=CS2n_yua4w@mail.gmail.com>
On Fri, May 29, 2026 at 04:57:06AM -0500, Simon Glass wrote:
[..]
> cached contents are still valid. Erase/write mutate device state, but
> flush does not. Please drop the blkcache_invalidate() call (and the
> matching one in the non-DM inline below).
>
> > diff --git a/include/blk.h b/include/blk.h
> > @@ -99,6 +99,7 @@ struct blk_desc {
> > unsigned long (*block_erase)(struct blk_desc *block_dev,
> > lbaint_t start,
> > lbaint_t blkcnt);
> > + unsigned long (*block_flush)(struct blk_desc *block_dev);
>
> This field lives in the !CONFIG_BLK (legacy) branch, but no legacy
> driver in the series wires it up. The only consumer (NVMe) is DM-only.
> Are you going to need the legacy plumbing?
blk_dflush() is used in flush subcommand in cmd/blk_common.c
(I also used it for tests in v3 of the upcoming series).
--
Denis
next prev parent reply other threads:[~2026-07-16 22:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 3:44 [PATCH v2 0/6] nvme: few fixups dmukhin
2026-05-29 3:44 ` [PATCH v2 1/6] drivers: nvme: Log I/O timeouts dmukhin
2026-05-29 9:56 ` Simon Glass
2026-05-29 3:44 ` [PATCH v2 2/6] drivers: block: Introduce blk_flush()/blk_dflush() dmukhin
2026-05-29 9:57 ` Simon Glass
2026-07-16 22:28 ` dmukhin [this message]
2026-05-29 3:44 ` [PATCH v2 3/6] drivers: nvme: Implement flush command dmukhin
2026-05-29 9:57 ` Simon Glass
2026-05-29 3:44 ` [PATCH v2 4/6] cmd: Add flush support for all blk devices dmukhin
2026-05-29 9:57 ` Simon Glass
2026-06-05 3:55 ` dmukhin
2026-06-03 17:43 ` Sean Anderson
2026-06-04 17:01 ` Simon Glass
2026-06-05 3:53 ` dmukhin
2026-05-29 3:44 ` [PATCH v2 5/6] drivers: nvme: Export nvme_shutdown() dmukhin
2026-05-29 9:57 ` Simon Glass
2026-05-29 3:44 ` [PATCH v2 6/6] docs: nvme: Update QEMU command for testing dmukhin
2026-05-29 9:58 ` Simon Glass
2026-05-29 9:58 ` [v2,0/6] nvme: few fixups Simon Glass
2026-06-03 16:22 ` (subset) [PATCH v2 0/6] " Neil Armstrong
2026-06-04 6:32 ` neil.armstrong
2026-06-05 3:59 ` 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=alla8U6P8/VE8tsG@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