Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>,
	"damien.lemoal@opensource.wdc.com"
	<damien.lemoal@opensource.wdc.com>
Subject: Re: [PATCH v2 1/2] stat: remove duplicated code in show_mixed_ddir_status()
Date: Mon, 17 Jan 2022 07:23:26 -0700	[thread overview]
Message-ID: <6aacebfa-9e60-0a67-bc04-73776df07f9f@kernel.dk> (raw)
In-Reply-To: <20220117110932.300809-1-Niklas.Cassel@wdc.com>

On 1/17/22 4:09 AM, Niklas Cassel wrote:
> From: Niklas Cassel <niklas.cassel@wdc.com>

[snip]

When sending more than one patch, please use a cover letter. Not
_strictly_ required, but I do prefer to see one as it's a natural place
to put the changelog (v1 -> v2, etc). If that isn't there, I do expect
to see a per-patch changelog in each patch.

-- 
Jens Axboe


      parent reply	other threads:[~2022-01-17 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 11:09 [PATCH v2 1/2] stat: remove duplicated code in show_mixed_ddir_status() Niklas Cassel
2022-01-17 11:09 ` [PATCH v2 2/2] stat: move unified=both mixed allocation and calculation to new helper Niklas Cassel
2022-01-17 14:23 ` Jens Axboe [this message]

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=6aacebfa-9e60-0a67-bc04-73776df07f9f@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Niklas.Cassel@wdc.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=fio@vger.kernel.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