From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] Add hard_irq_disable()
Date: Thu, 10 May 2007 01:53:28 -0700 (PDT) [thread overview]
Message-ID: <20070510.015328.104645983.davem@davemloft.net> (raw)
In-Reply-To: <20070510015036.ebded3ac.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Thu, 10 May 2007 01:50:36 -0700
> We discussed this a couple of months back. davem landed firmly in the
> second camp and everyone then shut up ;)
No I landed in the first :-)))
I think the empty lines are a waste and only serve to eat
up precious screen real-estate when reading code.
It is possible that I used to use the empty line thing in
the past, but I definitely don't do that any more.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: benh@kernel.crashing.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, rusty@rustcorp.com.au
Subject: Re: [PATCH 2/3] Add hard_irq_disable()
Date: Thu, 10 May 2007 01:53:28 -0700 (PDT) [thread overview]
Message-ID: <20070510.015328.104645983.davem@davemloft.net> (raw)
In-Reply-To: <20070510015036.ebded3ac.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Thu, 10 May 2007 01:50:36 -0700
> We discussed this a couple of months back. davem landed firmly in the
> second camp and everyone then shut up ;)
No I landed in the first :-)))
I think the empty lines are a waste and only serve to eat
up precious screen real-estate when reading code.
It is possible that I used to use the empty line thing in
the past, but I definitely don't do that any more.
next prev parent reply other threads:[~2007-05-10 8:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 5:25 [PATCH 2/3] Add hard_irq_disable() Benjamin Herrenschmidt
2007-05-10 5:25 ` Benjamin Herrenschmidt
2007-05-10 5:41 ` Andrew Morton
2007-05-10 5:41 ` Andrew Morton
2007-05-10 6:35 ` Benjamin Herrenschmidt
2007-05-10 6:35 ` Benjamin Herrenschmidt
2007-05-10 7:35 ` Andrew Morton
2007-05-10 7:35 ` Andrew Morton
2007-05-10 8:41 ` Benjamin Herrenschmidt
2007-05-10 8:41 ` Benjamin Herrenschmidt
2007-05-10 8:49 ` David Miller
2007-05-10 8:49 ` David Miller
2007-05-10 8:50 ` Andrew Morton
2007-05-10 8:50 ` Andrew Morton
2007-05-10 8:53 ` David Miller [this message]
2007-05-10 8:53 ` David Miller
2007-05-10 9:29 ` Benjamin Herrenschmidt
2007-05-10 9:29 ` Benjamin Herrenschmidt
2007-05-10 11:01 ` Josh Boyer
2007-05-10 11:01 ` Josh Boyer
2007-05-10 6:45 ` Satyam Sharma
2007-05-10 6:45 ` Satyam Sharma
2007-05-10 7:21 ` Benjamin Herrenschmidt
2007-05-10 7:21 ` Benjamin Herrenschmidt
2007-05-10 7:54 ` Satyam Sharma
2007-05-10 7:54 ` Satyam Sharma
2007-05-10 8:46 ` Benjamin Herrenschmidt
2007-05-10 8:46 ` Benjamin Herrenschmidt
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=20070510.015328.104645983.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.