From: Mike Travis <travis@sgi.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jack Steiner <steiner@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] cpumask: update local_cpus_show to use new cpumask API
Date: Mon, 05 Jan 2009 15:08:16 -0800 [thread overview]
Message-ID: <496292E0.5060403@sgi.com> (raw)
In-Reply-To: <200901051310.07147.jbarnes@virtuousgeek.org>
Jesse Barnes wrote:
> On Monday, January 5, 2009 12:33 pm Mike Travis wrote:
>> Impact: cleanup, reduce stack usage, use new cpumask API.
>>
>> Replace the local cpumask_t variable with a pointer to the
>> const cpumask that needs to be printed.
>>
>> Signed-off-by: Mike Travis <travis@sgi.com>
>> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
>> ---
>> drivers/pci/pci-sysfs.c | 12 ++++++------
>> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> Hm, clearly there are other patches in Ingo's tree that this depends on, since
> this patch assumes the presence of cpumask_of_pcibus and has slightly
> different cpumask_scnprintf context. I'll just let Ingo push the whole thing.
>
Ok, thanks. I saw that but I *think* all of this is in Linus' tree.
Cheers,
Mike
next prev parent reply other threads:[~2009-01-05 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 20:33 [PATCH 0/2] pci cpumask: remove local cpumask_t's from the stack Mike Travis
2009-01-05 20:33 ` [PATCH 1/2] cpumask: update local_cpus_show to use new cpumask API Mike Travis
2009-01-05 21:10 ` Jesse Barnes
2009-01-05 23:08 ` Mike Travis [this message]
2009-01-06 12:37 ` Ingo Molnar
2009-01-05 20:33 ` [PATCH 2/2] cpumask: update pci_bus_show_cpuaffinity " Mike Travis
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=496292E0.5060403@sgi.com \
--to=travis@sgi.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
/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