From: Evgeny Voevodin <e.voevodin@samsung.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] checkpatch: Don't WARN about missing spaces in audio files
Date: Fri, 10 Feb 2012 07:50:45 +0400 [thread overview]
Message-ID: <4F349415.2000507@samsung.com> (raw)
In-Reply-To: <1328799563-18932-1-git-send-email-afaerber@suse.de>
On 02/09/2012 06:59 PM, Andreas Färber wrote:
> Disable warnings for spaces before opening parenthesis in
> hw/{ac97,adlib,cs4231a,es1370,gus,sb16}.c.
Why audio files are such a special thing?
Isn't it be better to revert a patch that introduced checkpatch.pl errors?
--
Kind regards,
Evgeny Voevodin,
Leading Software Engineer,
ASWG, Moscow R&D center, Samsung Electronics
e-mail: e.voevodin@samsung.com
next prev parent reply other threads:[~2012-02-10 3:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 14:59 [Qemu-devel] [PATCH] checkpatch: Don't WARN about missing spaces in audio files Andreas Färber
2012-02-09 15:03 ` Andreas Färber
2012-02-09 16:43 ` malc
2012-02-10 3:50 ` Evgeny Voevodin [this message]
2012-02-10 4:02 ` malc
2012-02-10 17:47 ` Anthony Liguori
2012-02-11 9:44 ` Blue Swirl
2012-02-17 14:31 ` Anthony Liguori
2012-02-17 14:55 ` Markus Armbruster
2012-02-17 15:26 ` Anthony Liguori
2012-02-18 9:13 ` Blue Swirl
2012-02-18 10:56 ` Stefan Weil
2012-02-18 14:18 ` Anthony Liguori
2012-02-18 14:34 ` Blue Swirl
2012-02-18 15:53 ` Andreas Färber
2012-02-18 16:47 ` Eric Blake
2012-02-18 8:56 ` Blue Swirl
2012-02-18 9:07 ` [Qemu-devel] [PATCH] astyle: Formatting rules for QEMU Stefan Weil
2012-02-18 10:10 ` Blue Swirl
2012-02-18 11:13 ` Stefan Weil
2012-02-11 9:37 ` [Qemu-devel] [PATCH] checkpatch: Don't WARN about missing spaces in audio files Blue Swirl
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=4F349415.2000507@samsung.com \
--to=e.voevodin@samsung.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 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.