From: Linus Torvalds <torvalds@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ingo Molnar <mingo@elte.hu>, Mike Travis <travis@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PULL] Trivial macros to help cpumask conversion in linux-next: tsk_cpumask and mm_cpumask
Date: Tue, 3 Mar 2009 14:12:09 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0903031411320.3111@localhost.localdomain> (raw)
In-Reply-To: <200903031635.54296.rusty@rustcorp.com.au>
On Tue, 3 Mar 2009, Rusty Russell wrote:
>
> Rusty Russell (2):
> cpumask: tsk_cpumask for accessing the struct task_struct's cpus_allowed.
> cpumask: mm_cpumask for accessing the struct mm_struct's cpu_vm_mask.
I really want to know the _reason_ for things like this, not just a
trivial patch that adds a stupid macro "for the future".
Linus
next prev parent reply other threads:[~2009-03-03 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 6:05 Rusty Russell
2009-03-03 22:12 ` Linus Torvalds [this message]
2009-03-04 1:16 ` Rusty Russell
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=alpine.LFD.2.00.0903031411320.3111@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--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
all inboxes | Powered by JetHome®