From: Peter Maydell <peter.maydell@linaro.org>
To: Juan Quintela <quintela@redhat.com>
Cc: no-reply@patchew.org, "Cédric Le Goater" <clg@kaod.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Fam Zheng" <famz@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
joonas.lahtinen@linux.intel.com,
"Kirti Wankhede" <kwankhede@nvidia.com>,
zhenyuw@linux.intel.com, "Yulei Zhang" <yulei.zhang@intel.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
zhi.a.wang@intel.com,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v2] migration: discard non-migratable RAMBlocks
Date: Fri, 13 Apr 2018 12:53:13 +0100 [thread overview]
Message-ID: <CAFEAcA-ifRco0bKCbbSDGQkz33_jdP03mOB3+WJ3_zObcAisrA@mail.gmail.com> (raw)
In-Reply-To: <87d0z3pd6x.fsf@secure.laptop>
On 13 April 2018 at 12:18, Juan Quintela <quintela@redhat.com> wrote:
> no-reply@patchew.org wrote:
>> === OUTPUT BEGIN ===
>> Checking PATCH 1/1: migration: discard non-migratable RAMBlocks...
>> ERROR: Macros with multiple statements should be enclosed in a do - while loop
>> #96: FILE: migration/ram.c:191:
>> +#define RAMBLOCK_FOREACH_MIGRATABLE(block) \
>> + RAMBLOCK_FOREACH(block) \
>> + if (!qemu_ram_is_migratable(block)) {} else
>>
>> ERROR: trailing statements should be on next line
>> #98: FILE: migration/ram.c:193:
>> + if (!qemu_ram_is_migratable(block)) {} else
>>
>> total: 2 errors, 0 warnings, 167 lines checked
>
> To be fair, I don't know how to fix this outside of:
>
> BEGIN_RAMBLOCK_FOREACH(...)
>
> END_RAMBLOCK_FOREACH()
>
> type of construct. I was wondering about what could happen if the
> RAMBLOCK_FOREACH was insied an if, but checkpatch beated me to it.
RAMBLOCK_FOREACH inside if() should work fine here. I don't
think we can expect checkpatch to be able to cope with all
of the complicated macro magic we do, so if we're satisfied
that the macro is doing what we want then we should just
ignore the checkpatch error.
thanks
-- PMM
next prev parent reply other threads:[~2018-04-13 11:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 7:52 [Qemu-devel] [PATCH v2] migration: discard non-migratable RAMBlocks Cédric Le Goater
2018-04-13 7:56 ` no-reply
2018-04-13 11:18 ` Juan Quintela
2018-04-13 11:53 ` Peter Maydell [this message]
2018-04-19 16:58 ` Dr. David Alan Gilbert
2018-04-20 6:59 ` Cédric Le Goater
2018-04-20 8:47 ` Peter Maydell
2018-04-20 9:05 ` Cédric Le Goater
2018-05-09 11:08 ` Dr. David Alan Gilbert
2018-05-09 11:33 ` Peter Maydell
2018-05-09 11:54 ` Paolo Bonzini
2018-05-10 19:15 ` Dr. David Alan Gilbert
2018-05-10 21:43 ` Cédric Le Goater
2018-04-19 17:32 ` Peter Maydell
2018-04-19 17:45 ` Edgar E. Iglesias
2018-04-20 8:14 ` KONRAD Frederic
2018-04-20 9:24 ` Edgar E. Iglesias
2018-04-20 12:09 ` Peter Maydell
2018-04-21 8:52 ` Cédric Le Goater
2018-04-21 9:33 ` Peter Maydell
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=CAFEAcA-ifRco0bKCbbSDGQkz33_jdP03mOB3+WJ3_zObcAisrA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kwankhede@nvidia.com \
--cc=no-reply@patchew.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yulei.zhang@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.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).