From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
Bob Moore <robert.moore@intel.com>,
Lin Ming <ming.m.lin@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 5/7] acpi: fix a bunch of style issues on 'actypes.h'
Date: Mon, 19 Oct 2009 19:16:07 +0300 [thread overview]
Message-ID: <94a0d4530910190916t2bdd9ecl59a3cfc0cc732852@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0910191658260.8582@wotan.suse.de>
On Mon, Oct 19, 2009 at 6:03 PM, Jiri Kosina <jkosina@suse.cz> wrote:
> On Mon, 19 Oct 2009, Felipe Contreras wrote:
>
>> > I have never been in favor of merging whitespace-only patches (in a
>> > sense that the sole purpose of them being to change whitespaces, but
>> > no else value added).
>> If somebody tries to send a patch for that file that doesn't fix the
>> white-space, checkpatch will complain, and people will complain that
>> checkpatch complains, which is precisely what happened,
>
> Oh, well ... checkpatch warning about this is somewhat controversial. My
> preferred way would be that it warns about whitespace only if there are
> also some other (non-whitespace) changes.
Huh? I think we are talking about different things. See the next comment.
>> and I was requested to write this patch by Daniel Walker (final mail
>> wasn't on the ml):
>>
>> http://lkml.org/lkml/2009/9/14/183
>
> This is something slightly different -- he asks you to fixup whitespace
> issue in the code you are newly introducing, right?
No, did you read the thread?
This was my patch:
-#define ACPI_MIN(a,b) (((a)<(b))?(a):(b))
-#define ACPI_MAX(a,b) (((a)>(b))?(a):(b))
+#define ACPI_MIN(a,b) min(a, b)
+#define ACPI_MAX(a,b) max(a, b)
Checkpatch complains, even though my changes are ok. So that's what I
mean, if somebody wants to do a similar patch in the future so that
checkpatch doesn't complain; they would have to fix the white-spaces
again.
Or checkpatch should be fixed.
>> > And after today's discussion on kernel summit on this topic, I wouldn't
>> > expect any maintainer to merge it, sorry :)
>> What are you talking about?
>
> Seems like many kernel maintainers are just tired of
> 'whitespace-cleanup-only' patches that bring no real added value
> otherwise.
Hm, I wonder what would happen to the current badly formatted code.
Stay there forever?
--
Felipe Contreras
next prev parent reply other threads:[~2009-10-19 16:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1255906474-25091-1-git-send-email-felipe.contreras@gmail.com>
2009-10-18 22:54 ` [PATCH 4/7] acpi: processor: fix section mismatch Felipe Contreras
2009-11-04 13:28 ` Jiri Kosina
2009-11-12 0:30 ` Felipe Contreras
2009-10-18 22:54 ` [PATCH 5/7] acpi: fix a bunch of style issues on 'actypes.h' Felipe Contreras
2009-10-19 14:20 ` Jiri Kosina
2009-10-19 14:57 ` Felipe Contreras
2009-10-19 15:03 ` Jiri Kosina
2009-10-19 16:16 ` Felipe Contreras [this message]
2009-10-20 5:53 ` Artem Bityutskiy
2009-11-13 20:58 ` Daniel Walker
2009-11-13 21:08 ` Moore, Robert
2009-11-13 21:41 ` Jiri Kosina
2009-11-13 21:48 ` Daniel Walker
2009-10-18 22:54 ` [PATCH 6/7] acpi: fix trivial warning Felipe Contreras
2009-10-19 14:14 ` Jiri Kosina
2009-10-18 22:54 ` [PATCH 7/7] acpi: fix trivial warnings caused by previous commmit Felipe Contreras
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=94a0d4530910190916t2bdd9ecl59a3cfc0cc732852@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=jkosina@suse.cz \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox