From: David Reaver <me@davidreaver.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
Konstantin Khlebnikov <koct9i@gmail.com>,
linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: iostats: Rewrite intro, remove outdated formats
Date: Fri, 14 Feb 2025 07:56:26 -0800 [thread overview]
Message-ID: <86frkgy0yd.fsf@davidreaver.com> (raw)
In-Reply-To: <87frkgzfwg.fsf@trenco.lwn.net> (Jonathan Corbet's message of "Fri, 14 Feb 2025 08:48:15 -0700")
Jonathan Corbet <corbet@lwn.net> writes:
>
> As a separate thread is generally better; no need to resend, though, if
> there are no other changes.
>
Understood! Thanks.
> But ... I'm not quite sure what "mutually exclusive" means here. That
> they don't conflict, or that they cannot both be applied...?
Sorry, bad wording :) This patch conflicts with the original patch since
I rewrote that whole paragraph, so I ignore the first patch I sent.
Thanks,
David Reaver
next prev parent reply other threads:[~2025-02-14 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 1:39 [PATCH] docs: iostats: Update introduction with flush fields David Reaver
2025-02-14 2:21 ` Randy Dunlap
2025-02-14 5:14 ` [PATCH] docs: iostats: Rewrite intro, remove outdated formats David Reaver
2025-02-14 10:21 ` Bagas Sanjaya
2025-02-14 15:48 ` Jonathan Corbet
2025-02-14 15:56 ` David Reaver [this message]
[not found] ` <CALYGNiOU3vPAyvsNv4rt=qZRbZFVZ9iAe+kzPzGKkx6_L3wG5Q@mail.gmail.com>
2025-02-14 17:39 ` David Reaver
2025-02-15 17:18 ` Konstantin Khlebnikov
2025-02-15 17:29 ` David Reaver
2025-02-15 17:46 ` Konstantin Khlebnikov
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=86frkgy0yd.fsf@davidreaver.com \
--to=me@davidreaver.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=koct9i@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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).