From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
peter.portante@redhat.com, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/4] More whitespace and coding style clean ups ahead of future changes
Date: Thu, 22 Mar 2012 14:28:59 +0100 [thread overview]
Message-ID: <4F6B291B.4080200@siemens.com> (raw)
In-Reply-To: <4F6A6CCE.4000904@redhat.com>
On 2012-03-22 01:05, Paolo Bonzini wrote:
> Il 21/03/2012 22:02, Peter Portante ha scritto:
>> Hi Folks,
>>
>> Please forgive me if you find these changes are annoying, as I am trying to
>> learn the ropes of patch submission with git ahead of making a real patch.
>>
>> While working on the code, I found that scripts/checkpatch.pl will flag lines
>> that I am changing as not adhereing to the codeing standard due to
>> pre-existing coding violations. So I figured I could learn a bit about how to
>> submit patches by fixing these files I will be touching before submitting the
>> code changes.
>
> I think slirp is a mess and it's not worth doing this kind of sweeping
> change. Just ignore checkpatch output for slirp.
In fact, I could imagine accepting slirp cleanups provided they come in
palatable pieces and validate that the binary output is unchanged. It's
really a pain changing something in slirp having to use a totally
inconsistent style just to keep the code slightly readable.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-03-22 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 21:02 [Qemu-devel] [PATCH 0/4] More whitespace and coding style clean ups ahead of future changes Peter Portante
2012-03-21 21:02 ` [Qemu-devel] [PATCH 1/4] More whitespace cleanup in preparation for future commits Peter Portante
2012-03-21 21:02 ` [Qemu-devel] [PATCH 2/4] More work to fix up the formatting and the whitespace of this module to conform to the coding standard Peter Portante
2012-03-21 21:02 ` [Qemu-devel] [PATCH 3/4] And some final work to complete the coding style upgrade, missed by the previous commit Peter Portante
2012-03-21 21:02 ` [Qemu-devel] [PATCH 4/4] Yet another missed use of tabs Peter Portante
2012-03-22 0:05 ` [Qemu-devel] [PATCH 0/4] More whitespace and coding style clean ups ahead of future changes Paolo Bonzini
2012-03-22 10:27 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2012-03-22 13:28 ` Jan Kiszka [this message]
2012-03-22 10:57 ` [Qemu-devel] " 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=4F6B291B.4080200@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=peter.portante@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).