From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 00/19] irqchip: crossbar: driver fixes
Date: Fri, 13 Jun 2014 22:38:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1406132222570.5170@nanos> (raw)
In-Reply-To: <20140613165458.GS8664@titan.lakedaemon.net>
On Fri, 13 Jun 2014, Jason Cooper wrote:
> On Fri, Jun 13, 2014 at 09:48:24AM -0700, Joe Perches wrote:
> > On Fri, 2014-06-13 at 12:37 -0400, Jason Cooper wrote:
> > > On Fri, Jun 13, 2014 at 09:14:34AM -0700, Joe Perches wrote:
> > > > On Fri, 2014-06-13 at 11:01 -0400, Jason Cooper wrote:
> > > > > Please format the subject lines like so:
> > > > >
> > > > > irqchip: crossbar: Set cb pointer ...
> > > > > ^
> > > > > |
> > > > > \-- note the capitalization
> > > >
> > > > I suggest you don't make this a rule and focus
> > > > on more important stuff instead.
Says the one, who pesters people about typos in changelogs....
WTF? Jason is doing a great job in reviewing and he knows what to
concentrate on.
> > > It's not my rule. ;-)
> >
> > Who's rule is it then?
>
> Thomas'
Sentences start with an upper case letter. Our brain is trained on
that rule when parsing a line.
So for people who actually review patches by reading them instead of
running a spell checker, consistent formatting more important than
avoiding the random typo, which our brain just blends out in most of
the cases. Unfortunately also when the typo is in actual code :(
Thanks,
tglx
next prev parent reply other threads:[~2014-06-13 20:38 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 11:53 [PATCH V2 00/19] irqchip: crossbar: driver fixes Sricharan R
2014-06-12 11:53 ` [PATCH V2 01/19] irqchip: crossbar: dont use '0' to mark reserved interrupts Sricharan R
2014-06-12 11:53 ` [PATCH V2 02/19] irqchip: crossbar: check for premapped crossbar before allocating Sricharan R
2014-06-12 11:53 ` [PATCH V2 03/19] irqchip: crossbar: Skip some irqs from getting mapped to crossbar Sricharan R
2014-06-12 12:51 ` Jason Cooper
2014-06-12 13:19 ` Sricharan R
2014-06-12 14:07 ` Jason Cooper
2014-06-13 6:37 ` Sricharan R
2014-06-13 13:34 ` Jason Cooper
2014-06-12 13:57 ` Tony Lindgren
2014-06-12 14:05 ` Jason Cooper
2014-06-13 6:56 ` Sricharan R
2014-06-13 11:04 ` Sricharan R
2014-06-13 13:10 ` Jason Cooper
2014-06-13 13:35 ` Santosh Shilimkar
2014-06-13 13:41 ` Jason Cooper
2014-06-13 6:31 ` Sricharan R
2014-06-12 11:53 ` [PATCH V2 04/19] irqchip: crossbar: Initialise the crossbar with a safe value Sricharan R
2014-06-12 11:53 ` [PATCH V2 05/19] irqchip: crossbar: Change allocation logic by reversing search for free irqs Sricharan R
2014-06-12 12:56 ` Jason Cooper
2014-06-13 6:09 ` Sricharan R
2014-06-13 13:13 ` Jason Cooper
2014-06-12 11:53 ` [PATCH V2 06/19] irqchip: crossbar: remove IS_ERR_VALUE check Sricharan R
2014-06-12 11:53 ` [PATCH V2 07/19] irqchip: crossbar: fix sparse warnings Sricharan R
2014-06-12 11:53 ` [PATCH V2 08/19] irqchip: crossbar: fix checkpatch warning Sricharan R
2014-06-12 13:10 ` Jason Cooper
2014-06-12 13:35 ` Sricharan R
2014-06-12 14:18 ` Joe Perches
2014-06-12 15:32 ` Jason Cooper
2014-06-12 16:05 ` Joe Perches
2014-06-13 6:30 ` Sricharan R
2014-06-13 13:15 ` Jason Cooper
2014-06-12 11:53 ` [PATCH V2 09/19] irqchip: crossbar: fix kerneldoc warning Sricharan R
2014-06-12 13:14 ` Jason Cooper
2014-06-12 13:39 ` Sricharan R
2014-06-12 11:53 ` [PATCH V2 10/19] irqchip: crossbar: DRA7: Fix unused crossbar list Sricharan R
2014-06-12 13:16 ` Jason Cooper
2014-06-12 13:21 ` Sricharan R
2014-06-12 11:53 ` [PATCH V2 11/19] irqchip: crossbar: fix memory leak incase of invalid entry Sricharan R
2014-06-12 13:20 ` Jason Cooper
2014-06-12 13:37 ` Sricharan R
2014-06-12 11:53 ` [PATCH V2 12/19] irqchip: crossbar: return proper error value Sricharan R
2014-06-12 13:39 ` Jason Cooper
2014-06-12 11:53 ` [PATCH V2 13/19] irqchip: crossbar: change the goto naming Sricharan R
2014-06-12 13:41 ` Jason Cooper
2014-06-12 11:53 ` [PATCH V2 14/19] irqchip: crossbar: set cb pointer to null in case of error Sricharan R
2014-06-12 11:53 ` [PATCH V2 15/19] irqchip: crossbar: Add kerneldoc for crossbar_domain_unmap callback Sricharan R
2014-06-12 13:49 ` Jason Cooper
2014-06-12 13:50 ` Sricharan R
2014-06-12 11:53 ` [PATCH V2 16/19] irqchip: crossbar: introduce ti, max-crossbar-sources to identify valid crossbar mapping Sricharan R
2014-06-12 13:54 ` [PATCH V2 16/19] irqchip: crossbar: introduce ti,max-crossbar-sources " Jason Cooper
2014-06-13 10:54 ` [PATCH V2 16/19] irqchip: crossbar: introduce ti, max-crossbar-sources " Sricharan R
2014-06-13 13:17 ` [PATCH V2 16/19] irqchip: crossbar: introduce ti,max-crossbar-sources " Jason Cooper
2014-06-12 11:53 ` [PATCH V2 17/19] irqchip: crossbar: introduce centralized check for crossbar write Sricharan R
2014-06-12 11:53 ` [PATCH V2 18/19] Documentation: dt: OMAP: crossbar: add description for interrupt consumer Sricharan R
2014-06-12 11:53 ` [PATCH V2 19/19] irqchip: crossbar allow for quirky hardware with direct hardwiring of GIC Sricharan R
2014-06-13 15:01 ` [PATCH V2 00/19] irqchip: crossbar: driver fixes Jason Cooper
2014-06-13 16:14 ` Joe Perches
2014-06-13 16:37 ` Jason Cooper
2014-06-13 16:48 ` Joe Perches
2014-06-13 16:54 ` Jason Cooper
2014-06-13 20:38 ` Thomas Gleixner [this message]
2014-06-13 22:22 ` Joe Perches
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=alpine.DEB.2.10.1406132222570.5170@nanos \
--to=tglx@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.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