qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: no-reply@ec2-52-6-146-230.compute-1.amazonaws.com,
	famz@redhat.com, ehabkost@redhat.com, mst@redhat.com,
	qemu-devel@nongnu.org, peterx@redhat.com,
	jan kiszka <jan.kiszka@web.de>,
	rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] checkpatch: allow tabs in linux-headers
Date: Tue, 9 Aug 2016 18:57:32 +0200	[thread overview]
Message-ID: <20160809165731.GB11647@potion> (raw)
In-Reply-To: <4ba6911e-08d5-bbd2-2125-eb3213a4df77@redhat.com>

2016-08-09 18:39+0200, Paolo Bonzini:
> On 09/08/2016 18:37, Radim Krčmář wrote:
>>>> Make scripts/checkpatch.pl accept tabs in linux-headers/, instead of
>>>> changing scripts/update-linux-headers.sh to expand tabs when importing.
>>>>
>>>> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
>>>> ---
>>>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>>>> index 929708721299..38232d4b25c3 100755
>>>> --- a/scripts/checkpatch.pl
>>>> +++ b/scripts/checkpatch.pl
>>>> @@ -1355,7 +1355,7 @@ sub process {
>>>>  		next if ($realfile !~ /\.(h|c|cpp|pl)$/);
>>>>  
>>>>  # in QEMU, no tabs are allowed
>>>> -		if ($rawline =~ /^\+.*\t/) {
>>>> +		if ($rawline =~ /^\+.*\t/ && $realfile !~ /^linux-headers\//) {
>>>>  			my $herevet = "$here\n" . cat_vet($rawline) . "\n";
>>>>  			ERROR("code indent should never use tabs\n" . $herevet);
>>>>  			$rpt_cleaners = 1;
>>>>
>>>
>>> Could you do the same for standard-headers/ too?
>> 
>> Sure, and when we are at it ... are *.pl files going to be reindented?
>> 
>> e.g. checkpatch.pl uses tabs consistently, get_maintainer.pl is a
>> horrible mix of tabs and spaces [1], and clean-header-guards.pl uses 4
>> spaces for an indent.
> 
> I've sent a patch series to fix the most obvious issues in automated
> checkpatch email, it skips the tab check on imported Perl scripts.

I will base on that, thanks.

  reply	other threads:[~2016-08-09 16:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 15:03 [Qemu-devel] [PATCH for-2.7 0/2] intel-iommu: restrict EIM to quirkless KVM Radim Krčmář
2016-08-09 15:03 ` [Qemu-devel] [PATCH 1/2] linux-headers: update to v4.8-rc1 Radim Krčmář
2016-08-09 16:11   ` Radim Krčmář
2016-08-09 15:03 ` [Qemu-devel] [PATCH 2/2] intel-iommu: restrict EIM to quirkless KVM Radim Krčmář
2016-08-10  3:29   ` Peter Xu
2016-08-10 16:59     ` Radim Krčmář
2016-08-11  3:33       ` Peter Xu
2016-08-09 15:31 ` [Qemu-devel] [PATCH for-2.7 0/2] " no-reply
2016-08-09 16:07   ` [Qemu-devel] [PATCH] checkpatch: allow tabs in linux-headers Radim Krčmář
2016-08-09 16:14     ` Paolo Bonzini
2016-08-09 16:37       ` Radim Krčmář
2016-08-09 16:39         ` Paolo Bonzini
2016-08-09 16:57           ` Radim Krčmář [this message]
2016-08-10  7:09       ` Cornelia Huck
2016-08-10 13:55         ` Radim Krčmář
2016-08-10 14:01           ` Cornelia Huck
2016-08-09 17:32     ` no-reply

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=20160809165731.GB11647@potion \
    --to=rkrcmar@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=famz@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=mst@redhat.com \
    --cc=no-reply@ec2-52-6-146-230.compute-1.amazonaws.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).