From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: add include/block/aio-wait.h
Date: Tue, 13 Mar 2018 01:05:19 +0800 [thread overview]
Message-ID: <20180312170519.GB8326@lemon.usersys.redhat.com> (raw)
In-Reply-To: <d47e7441-0166-07c6-20fd-6020e553903a@redhat.com>
On Mon, 03/12 09:05, Eric Blake wrote:
> On 03/12/2018 08:22 AM, Stefan Hajnoczi wrote:
> > The include/block/aio-wait.h header file was added by commit
> > 7719f3c968c59e1bcda7e177679dc765b59e578f ("block: extract
> > AIO_WAIT_WHILE() from BlockDriverState") without updating MAINTAINERS.
>
> A shame checkpatch.pl and/or patchew still doesn't flag this, even though
> it's been proposed as a syntax check.
Re checkpatch.pl vs patchew, IMO this check fits better in the former.
Fam
next prev parent reply other threads:[~2018-03-12 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 13:22 [Qemu-devel] [PATCH] MAINTAINERS: add include/block/aio-wait.h Stefan Hajnoczi
2018-03-12 14:05 ` Eric Blake
2018-03-12 17:05 ` Fam Zheng [this message]
2018-03-13 10:26 ` Stefan Hajnoczi
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=20180312170519.GB8326@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).