From: Sven-Thorsten Dietrich <sdietrich@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: dwalker@mvista.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch] IPV4 spinlock_casting
Date: Mon, 08 Aug 2005 12:54:25 -0700 [thread overview]
Message-ID: <1123530866.20053.12.camel@imap.mvista.com> (raw)
In-Reply-To: <20050808090659.GA11879@elte.hu>
On Mon, 2005-08-08 at 11:06 +0200, Ingo Molnar wrote:
>
> it just occured to me that !PREEMPT_RT builds would be affected by the
> #else branch, so i committed the build fix below into -52-15.
>
> Ingo
>
That fixes it. Thanks
Sven
> Index: linux/net/ipv4/route.c
> ===================================================================
> --- linux.orig/net/ipv4/route.c
> +++ linux/net/ipv4/route.c
> @@ -231,7 +231,7 @@ static spinlock_t *rt_hash_locks;
> spin_lock_init(&rt_hash_locks[i]); \
> }
> #else
> -# define rt_hash_lock_addr(slot) NULL
> +# define rt_hash_lock_addr(slot) ((spinlock_t *)NULL)
> # define rt_hash_lock_init()
> #endif
>
>
prev parent reply other threads:[~2005-08-08 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 2:04 [patch] IPV4 spinlock_casting Sven-Thorsten Dietrich
2005-08-08 9:04 ` Ingo Molnar
2005-08-08 9:06 ` Ingo Molnar
2005-08-08 19:54 ` Sven-Thorsten Dietrich [this message]
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=1123530866.20053.12.camel@imap.mvista.com \
--to=sdietrich@mvista.com \
--cc=dwalker@mvista.com \
--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