From: "David S. Miller" <davem@redhat.com>
To: rusty@rustcorp.com.au
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Simplify net/flow.c
Date: Fri, 23 Jan 2004 21:30:13 -0800 (PST) [thread overview]
Message-ID: <20040123.213013.41659820.davem@redhat.com> (raw)
In-Reply-To: <20040124050843.320902C056@lists.samba.org>
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Fri, 23 Jan 2004 17:55:28 +1100
In message <20040122195104.31cc2496.akpm@osdl.org> you write:
> - down(&cpucontrol);
> + down_cpucontrol();
OK. Although I think I prefer to have down_cpucontrol() defined under
#ifdef CONFIG_HOTPLUG_CPU, and revert to using a normal sem here as
well to cover the CONFIG_HOTPLUG_CPU=n CONFIG_SMP=y case. But I will
produce an additional patch with the hotplug cpu patches.
Rusty take a look at Linus's current BK tree, it should be
to your satisfaction I think :)
next prev parent reply other threads:[~2004-01-24 5:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 7:49 [PATCH] Simplify net/flow.c Rusty Russell
2004-01-22 18:10 ` David S. Miller
2004-01-23 3:51 ` Andrew Morton
2004-01-23 6:55 ` Rusty Russell
2004-01-24 5:30 ` David S. Miller [this message]
2004-01-23 7:16 ` David S. Miller
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=20040123.213013.41659820.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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.