From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Two trivial whitespace fixes in lockdep/spinlock code
Date: Tue, 3 Jul 2007 17:16:06 -0700 [thread overview]
Message-ID: <20070703171606.fb027c2b.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707040213340.11634@jikos.suse.cz>
On Wed, 4 Jul 2007 02:14:42 +0200 (CEST) Jiri Kosina <jkosina@suse.cz> wrote:
> From: Jiri Kosina <jkosina@suse.cz>
>
> Two trivial whitespace fixes in lockdep/spinlock code
>
> Cc: Ingo Molnar <mingo@elte.hu>
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
>
> diff --git a/kernel/lockdep.c b/kernel/lockdep.c
> index 1a5ff22..12ca5fd 100644
> --- a/kernel/lockdep.c
> +++ b/kernel/lockdep.c
> @@ -1222,7 +1222,7 @@ register_lock_class(struct lockdep_map *lock, unsigned int subclass, int force)
>
> /*
> * Debug-check: all keys must be persistent!
> - */
> + */
> if (!static_obj(lock->key)) {
> debug_locks_off();
> printk("INFO: trying to register non-static key.\n");
> diff --git a/kernel/spinlock.c b/kernel/spinlock.c
> index 2c6c2bf..5386d7e 100644
> --- a/kernel/spinlock.c
> +++ b/kernel/spinlock.c
> @@ -28,7 +28,7 @@ int __lockfunc _spin_trylock(spinlock_t *lock)
> spin_acquire(&lock->dep_map, 0, 1, _RET_IP_);
> return 1;
> }
> -
> +
> preempt_enable();
> return 0;
> }
Too trivial, sorry: we could generate 8 million patches like this.
next prev parent reply other threads:[~2007-07-04 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 0:14 [PATCH] Two trivial whitespace fixes in lockdep/spinlock code Jiri Kosina
2007-07-04 0:16 ` Andrew Morton [this message]
2007-07-09 17:45 ` Daniel Walker
2007-07-09 18:14 ` Andrew Morton
2007-07-04 8:29 ` Ingo Molnar
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=20070703171606.fb027c2b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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