qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Markus Armbruster <armbru@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] checkpatch.pl question
Date: Fri, 06 Jun 2014 16:33:45 +1000	[thread overview]
Message-ID: <539160C9.9070107@ozlabs.ru> (raw)
In-Reply-To: <87a99qr1r7.fsf@blackfin.pond.sub.org>

On 06/06/2014 04:27 PM, Markus Armbruster wrote:
> Alexey Kardashevskiy <aik@ozlabs.ru> writes:
> 
>> Hi!
>>
>> checkpatch.pl often complains on things like this:
>>
>> ===
>> ERROR: need consistent spacing around '*' (ctx:WxV)
>> #57: FILE: hw/misc/vfio.c:4323:
>> +int vfio_container_ioctl(AddressSpace *as, int32_t groupid,
>>                                        ^
>>
>> total: 1 errors, 0 warnings, 46 lines checked
>> ===
>>
>> Since perl is a write-only language, I cannot understand why :) Any clue?
> 
> It misinterprets the '*' as infix operator, because it doesn't recognize
> 'AddressSpace *as' is a declaration.  Sorry, this isn't much of a clue,
> but you didn't provide much of a reproducer.
> 

Ooops. Sorry about that.

The failing patch has been posted today:
[PATCH v8 2/4] vfio: Add vfio_container_ioctl()

And the failing chunk is:

diff --git a/include/hw/misc/vfio.h b/include/hw/misc/vfio.h
new file mode 100644
index 0000000..0b26cd8
--- /dev/null
+++ b/include/hw/misc/vfio.h
@@ -0,0 +1,9 @@
+#ifndef VFIO_API_H
+#define VFIO_API_H
+
+#include "qemu/typedefs.h"
+
+extern int vfio_container_ioctl(AddressSpace *as, int32_t groupid,
+                                int req, void *param);
+
+#endif




-- 
Alexey

  reply	other threads:[~2014-06-06  6:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  3:37 [Qemu-devel] checkpatch.pl question Alexey Kardashevskiy
2014-06-06  6:27 ` Markus Armbruster
2014-06-06  6:33   ` Alexey Kardashevskiy [this message]
2014-06-06  7:17     ` Markus Armbruster
2014-06-07 14:58       ` Peter Maydell
2014-06-07 16:00         ` Stefan Weil
2014-06-07 16:27           ` Peter Maydell
2014-06-08  8:32             ` Paolo Bonzini

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=539160C9.9070107@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=armbru@redhat.com \
    --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).