linux-kernel - Re: [PULL] Trivial macros to help cpumask conversion in linux-next: tsk_cpumask and mm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 Mar 2009 14:12:09 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
cc:	Ingo Molnar <mingo@...e.hu>, Mike Travis <travis@....com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PULL] Trivial macros to help cpumask conversion in linux-next:
 tsk_cpumask and mm_cpumask



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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/