The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: torvalds@linux-foundation.org, hch@infradead.org, mingo@elte.hu,
	rminnich@sandia.gov, ericvh@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] poll: allow f_op->poll to sleep, take #2
Date: Sat, 22 Nov 2008 02:31:49 +0900	[thread overview]
Message-ID: <4926F085.4060903@kernel.org> (raw)
In-Reply-To: <E1L3Zif-0008SF-S1@pomaz-ex.szeredi.hu>

Miklos Szeredi wrote:
> On Sat, 22 Nov 2008, Tejun Heo wrote:
>> For both, I was trying to stay consistent with the environment.  I
>> find mixed styles in close proximity much uglier than slightly
>> different but consistent style.  Eh... Is the consensus checkpatch or
>> die?
> 
> I think some common sense can be applied in these cases.  For example
> a small amount of offending style in close proximity can be fixed as
> well, as long as it doesn't interfere too much with the readability of
> the patch.

Well, yeah, given that fs/select.c is not a very hot file.  Introduced
inconsistencies are gonna stay there for a long time.  The two issues
in this patch is minor and can be easily adjusted but in general I'm
not too sure whether always sticking with checkpatch is a good idea
especially on fairly cold areas.  Anyways, I'll fix it up.

Thanks.

-- 
tejun

  reply	other threads:[~2008-11-21 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <491BA16C.30606@kernel.org>
     [not found] ` <alpine.LFD.2.00.0811151208430.3468@nehalem.linux-foundation.org>
2008-11-20 13:57   ` [PATCH RESEND] poll: allow f_op->poll to sleep, take #2 Tejun Heo
2008-11-21 16:42     ` Miklos Szeredi
2008-11-21 17:11       ` Tejun Heo
2008-11-21 17:23         ` Miklos Szeredi
2008-11-21 17:31           ` Tejun Heo [this message]
2008-11-22  7:28             ` [PATCH] poll: allow f_op->poll to sleep, take #3 Tejun Heo

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=4926F085.4060903@kernel.org \
    --to=tj@kernel.org \
    --cc=ericvh@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mingo@elte.hu \
    --cc=rminnich@sandia.gov \
    --cc=torvalds@linux-foundation.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