From: Jim Meyering <jim@meyering.net>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] checkpatch issue
Date: Thu, 10 May 2012 18:30:17 +0200 [thread overview]
Message-ID: <873978robq.fsf@rho.meyering.net> (raw)
In-Reply-To: <4FAB9412.4020306@redhat.com> (Gerd Hoffmann's message of "Thu, 10 May 2012 12:10:26 +0200")
Gerd Hoffmann wrote:
> anyone can explain what checkpatch tries to tell me here?
>
> ERROR: need consistent spacing around '*' (ctx:WxV)
> #11: FILE: hw/usb/hcd-ehci.c:1398:
> +static int ehci_execute(EHCIPacket *p)
Hi Gerd,
When I add that line to that file, creating the patch below,
checkpatch does not complain (Fedora 17's perl):
$ git fp --stdout -1 > k
$ scripts/checkpatch.pl k
total: 0 errors, 0 warnings, 11 lines checked
k has no obvious style problems and is ready for submission.
Regardless, maybe you can placate it by adding a "struct" before
the typedef's EHCIPacket.
>From 49f786191ab2a8176eb44a78e3d5ba44da6e10b6 Mon Sep 17 00:00:00 2001
From: Jim Meyering <meyering@redhat.com>
Date: Thu, 10 May 2012 18:25:51 +0200
Subject: [PATCH] .
Signed-off-by: Jim Meyering <meyering@redhat.com>
---
hw/usb/hcd-ehci.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/hw/usb/hcd-ehci.c b/hw/usb/hcd-ehci.c
index 4ff4d40..c9ccce9 100644
--- a/hw/usb/hcd-ehci.c
+++ b/hw/usb/hcd-ehci.c
@@ -2315,6 +2315,11 @@ static void ehci_register_types(void)
type_register_static(&ich9_ehci_info);
}
+static int ehci_execute(EHCIPacket *p)
+{
+}
+
+
type_init(ehci_register_types)
/*
--
1.7.10.1.487.ga3935e6
prev parent reply other threads:[~2012-05-10 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 10:10 [Qemu-devel] checkpatch issue Gerd Hoffmann
2012-05-10 10:28 ` Max Filippov
2012-05-10 16:30 ` Jim Meyering [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=873978robq.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=kraxel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.