From: Greg KH <gregkh@suse.de>
To: Mike Travis <travis@sgi.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@redhat.com>, Jack Steiner <steiner@sgi.com>,
linux-kernel@vger.kernel.org,
Ben Hutchings <bhutchings@solarflare.com>
Subject: Re: [PATCH 1/1]: sysfs: add documentation to cputopology.txt for system cpumasks
Date: Wed, 17 Dec 2008 18:58:40 -0800 [thread overview]
Message-ID: <20081218025840.GA18326@suse.de> (raw)
In-Reply-To: <494979C6.7060003@sgi.com>
On Wed, Dec 17, 2008 at 02:14:30PM -0800, Mike Travis wrote:
> Subject: sysfs: add documentation to cputopology.txt for system cpumasks
>
> Add information to cputopology.txt explaining the output of various
> system cpumask's.
>
> Signed-off-by: Mike Travis <travis@sgi.com>
Looks good to me, thanks for doing this.
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
next prev parent reply other threads:[~2008-12-18 2:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 4:26 [PATCH 0/3] x86/cpumask: fixups and additions Mike Travis
2008-12-16 4:26 ` [PATCH 1/3] x86: fix cpu_mask_to_apicid_and to include cpu_online_mask Mike Travis
2008-12-16 4:26 ` [PATCH 2/3] x86: use possible_cpus=NUM to extend the possible cpus allowed Mike Travis
2008-12-16 4:26 ` [PATCH 3/3] cpumask: add sysfs displays for configured and disabled cpu maps Mike Travis
2008-12-17 11:53 ` Rusty Russell
2008-12-17 18:40 ` Greg KH
2008-12-17 20:35 ` Mike Travis
2008-12-17 22:14 ` [PATCH 1/1]: sysfs: add documentation to cputopology.txt for system cpumasks Mike Travis
2008-12-18 2:58 ` Greg KH [this message]
2008-12-19 6:46 ` [PATCH 3/3] cpumask: add sysfs displays for configured and disabled cpu maps Rusty Russell
2008-12-19 16:15 ` Greg KH
[not found] ` <20081216114459.GA21266@elte.hu>
2008-12-17 23:01 ` [PATCH 0/3] x86/cpumask: fixups and additions 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=20081218025840.GA18326@suse.de \
--to=gregkh@suse.de \
--cc=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=steiner@sgi.com \
--cc=travis@sgi.com \
/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