Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jeff Furlong <jeff.furlong@wdc.com>, Jens Axboe <axboe@kernel.dk>
Cc: fio <fio@vger.kernel.org>
Subject: Re: [PATCH v2] fix windows cpu count
Date: Fri, 02 Nov 2018 11:24:04 -0700	[thread overview]
Message-ID: <1541183044.154300.2.camel@acm.org> (raw)
In-Reply-To: <MWHPR04MB0320BE1571FFF5497958BD6F8FCF0@MWHPR04MB0320.namprd04.prod.outlook.com>

On Fri, 2018-11-02 at 17:49 +0000, Jeff Furlong wrote:
> Sorry about the mixup, seems my email client had some updates and is stuck
> in quoted printable.  I'll try to resolve.

Hi Jeff,

A few months ago I documented on https://connect.wdc.com/ how to use git
send-email inside WDC. I think git send-email formats patches in the way Jens
expects them.

Bart.


      parent reply	other threads:[~2018-11-02 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 17:04 [PATCH v2] fix windows cpu count Jeff Furlong
2018-11-02 17:20 ` Jens Axboe
2018-11-02 17:49   ` Jeff Furlong
2018-11-02 18:03     ` Jens Axboe
2018-11-02 18:21       ` Jeff Furlong
2018-11-02 18:24     ` Bart Van Assche [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=1541183044.154300.2.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jeff.furlong@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox