From: Dave Jones <davej@redhat.com>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [PATCH] replace for_each_cpu with for_each_cpu_mask
Date: Fri, 11 Jun 2004 14:29:19 +0100 [thread overview]
Message-ID: <20040611132919.GF8779@redhat.com> (raw)
In-Reply-To: <20040611131855.GI1095@poupinou.org>
On Fri, Jun 11, 2004 at 03:18:55PM +0200, Bruno Ducrot wrote:
> On Fri, Jun 11, 2004 at 01:27:14PM +0100, Dave Jones wrote:
> > On Fri, Jun 11, 2004 at 12:09:12PM +0200, Bruno Ducrot wrote:
> >
> > > > That's indeed shorter -- don't know why whoever converted p4-clockmod
> > > > to the new sibling mask did use for_each_cpu_mask...
> > I think I found out why.
> >
> > > Something like that should be ok, I guess.
> > for_each_cpu_mask doesn't exist on non-SMP in mainline.
> Well, you mean it's not in 2.6.7-rc3? I will take a look.
Yeah, ISTR there's a considerable reworking of the cpu mask stuff
in -mm, which is what you based on iirc.
Dave
next prev parent reply other threads:[~2004-06-11 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 10:09 [PATCH] replace for_each_cpu with for_each_cpu_mask Bruno Ducrot
2004-06-11 12:27 ` Dave Jones
2004-06-11 13:18 ` Bruno Ducrot
2004-06-11 13:29 ` Dave Jones [this message]
2004-06-11 15:40 ` Bruno Ducrot
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=20040611132919.GF8779@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.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 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.