From: "Andreas Färber" <afaerber@suse.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Don Slutz <Don@cloudswitch.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/4] CHECKPATCH: Add warning for single else statement.
Date: Thu, 06 Sep 2012 12:32:01 +0200 [thread overview]
Message-ID: <50487BA1.6040608@suse.de> (raw)
In-Reply-To: <CAAu8pHvyiBkVyUxdKv1hT82TCytwkHiyzV49Abmb2DKgzhjQKA@mail.gmail.com>
Am 05.09.2012 21:46, schrieb Blue Swirl:
> Thanks, applied all.
Question: Are additions to checkpatch.pl supposed to be in QEMU Coding
Style as done here? Do you plan to convert it consistently then?
checkpatch.pl uses tabs consistently, making checkpatch.pl complain. ;)
The alternative would be to stick to upstream formatting and exempt
checkpatch.pl from its own checks.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-09-06 10:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 15:57 [Qemu-devel] [PATCH] CHECKPATCH Don Slutz
2012-09-01 15:57 ` [Qemu-devel] [PATCH] CHECKPATCH: Add warning for single else statement Don Slutz
2012-09-02 10:52 ` Blue Swirl
2012-09-02 10:51 ` [Qemu-devel] [PATCH] CHECKPATCH Blue Swirl
2012-09-06 15:32 ` Avi Kivity
2012-09-08 7:33 ` Blue Swirl
2012-09-02 23:22 ` [Qemu-devel] [PATCH v2 0/4] CHECKPATCH: Add warning for single else statement Don Slutz
2012-09-05 19:46 ` Blue Swirl
2012-09-06 10:32 ` Andreas Färber [this message]
2012-09-08 7:08 ` Blue Swirl
2012-09-02 23:22 ` [Qemu-devel] [PATCH v2 1/4] CHECKPATCH: Add --debug adv_dcs Don Slutz
2012-09-02 23:22 ` [Qemu-devel] [PATCH v2 2/4] CHECKPATCH: Add --debug adv_checking Don Slutz
2012-09-02 23:22 ` [Qemu-devel] [PATCH v2 3/4] CHECKPATCH: Add --debug adv_apw Don Slutz
2012-09-02 23:22 ` [Qemu-devel] [PATCH v2 4/4] CHECKPATCH: Add warning for single else statement Don Slutz
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=50487BA1.6040608@suse.de \
--to=afaerber@suse.de \
--cc=Don@cloudswitch.com \
--cc=blauwirbel@gmail.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.