public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	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: Tue, 20 Oct 2009 08:53:19 +0300	[thread overview]
Message-ID: <1256017999.29856.46.camel@localhost> (raw)
In-Reply-To: <alpine.LSU.2.00.0910191658260.8582@wotan.suse.de>

On Mon, 2009-10-19 at 17:03 +0200, Jiri Kosina 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.
> 
> > 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?
> 
> > > 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.

May be some are tired, but others just say thanks and apply them,
because it is easier to apply than complain, and because they do not
mind if their subsystem becomes a tiny bit cleaner. Sometimes it may
cause troubles, but hey, development is not easy and we are accustomed
to fix conflict and amend patches. But the include/acpi/actypes.h does
not seem to be changing very often anyway.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)


  parent reply	other threads:[~2009-10-20  5:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 22:54 [PATCH 0/7] trivial: fix some compilation warnings for 2.6.32-rc5 Felipe Contreras
2009-10-18 22:54 ` [PATCH 1/7] usb: trivial cleanups Felipe Contreras
2009-10-18 23:09   ` Felipe Contreras
2009-10-19 13:59     ` Alan Stern
2009-10-19 14:03       ` Felipe Contreras
2009-10-19 14:14         ` Alan Stern
2009-10-19  0:02   ` Greg KH
2009-10-19  1:04     ` Felipe Contreras
2009-10-18 22:54 ` [PATCH 2/7] ipc: fix trivial warning Felipe Contreras
2009-10-19 14:12   ` Jiri Kosina
2009-10-19 14:50     ` Felipe Contreras
2009-10-19 14:57       ` Jiri Kosina
2009-10-19 15:15         ` Felipe Contreras
2009-10-19 15:29           ` Jiri Kosina
2009-10-19 16:49             ` Felipe Contreras
2009-10-19 22:50               ` Jiri Kosina
2009-11-12  0:28                 ` Felipe Contreras
2009-11-12  1:13                   ` Jiri Kosina
2009-10-18 22:54 ` [PATCH 3/7] crypto: testmgr: fix warning Felipe Contreras
2009-10-19 13:52   ` Jiri Kosina
2009-10-19 13:58     ` Jarod Wilson
2009-10-19 14:03       ` Jarod Wilson
2009-11-12  0:32         ` Felipe Contreras
2009-11-12  0:43           ` Herbert Xu
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
2009-10-20  5:53         ` Artem Bityutskiy [this message]
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=1256017999.29856.46.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=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