From: Kevin Wolf <kwolf@redhat.com>
To: Connor Kuehl <ckuehl@redhat.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: Re: [PATCH v2 0/2] Clarify error messages pertaining to 'node-name'
Date: Mon, 8 Mar 2021 12:56:40 +0100 [thread overview]
Message-ID: <20210308115640.GD7021@merkur.fritz.box> (raw)
In-Reply-To: <20210305151929.1947331-1-ckuehl@redhat.com>
Am 05.03.2021 um 16:19 hat Connor Kuehl geschrieben:
> v2:
> - Moved summary into patch #1
> - Updated test cases that were missed in v1 from running 'make check'.
> This time I used 'make check-block SPEED=thorough' and some more
> grepping to make sure I didn't miss any.
> - Rebased
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2021-03-08 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 15:19 [PATCH v2 0/2] Clarify error messages pertaining to 'node-name' Connor Kuehl
2021-03-05 15:19 ` [PATCH v2 1/2] block: " Connor Kuehl
2021-03-05 15:19 ` [PATCH v2 2/2] blockdev: " Connor Kuehl
2021-03-08 11:56 ` Kevin Wolf [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=20210308115640.GD7021@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=ckuehl@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).