linux-kernel - Re: 'struct task_struct' has no member named 'mems

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20070112141004.71fbd023.pj@sgi.com>
Date:	Fri, 12 Jan 2007 14:10:04 -0800
From:	Paul Jackson <pj@....com>
To:	Christoph Lameter <clameter@....com>
Cc:	akpm@...l.org, sander@...ilis.net, linux-kernel@...r.kernel.org
Subject: Re: 'struct task_struct' has no member named 'mems_allowed'  (was:
 Re: 2.6.20-rc4-mm1)

Christoph wrote:
> If this is hidden in a macro then it may be overlooked.

Sooner or later, every line of code is important.

Shouting any one of them in #ifdef brackets creates
a noisier environment, increasing the chance of missing
another.

And besides ... the other umpteen cpuset hooks all use the
cpuset_*() style macros (except for fs/proc/base.c, which
has its own style ...).

Consistency in style is important in these matters.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
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/