linux-kernel - Re: [PATCHSET -mm] bitmap, cpumask, nodemask: implement pr

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: <20141210134944.0599597b96026cf2f1597e45@linux-foundation.org>
Date:	Wed, 10 Dec 2014 13:49:44 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCHSET -mm] bitmap, cpumask, nodemask: implement pr_cont
 functions and use di"

On Wed, 10 Dec 2014 10:52:42 -0500 Tejun Heo <tj@...nel.org> wrote:

>  0001-bitmap-restructure-bitmap_sn-list-printf.patch
>  0002-bitmap-cpumask-nodemask-implement-pr_cont-variants-o.patch
>  0003-mips-use-cpu-node-mask-pr_cont-and-seq-output-functi.patch
>  0004-powerpc-use-cpu-node-mask-pr_cont-and-seq-output-fun.patch
>  0005-tile-use-cpu-node-mask-pr_cont-and-seq-output-functi.patch
>  0006-x86-use-cpu-node-mask-pr_cont-and-seq-output-functio.patch
>  0007-xtensa-use-cpu-node-mask-pr_cont-and-seq-output-func.patch
>  0008-cpuset-use-cpu-node-mask-pr_cont-and-seq-output-func.patch
>  0009-rcu-use-cpu-node-mask-pr_cont-and-seq-output-functio.patch
>  0010-sched-use-cpu-node-mask-pr_cont-and-seq-output-funct.patch
>  0011-timer-use-cpu-node-mask-pr_cont-and-seq-output-funct.patch
>  0012-percpu-use-cpu-node-mask-pr_cont-and-seq-output-func.patch
> 
> The first two patches implement the pr_cont variants of the formatting
> functions.  The rest convert the existing users to pr_cont and seq
> functions subsystem-by-subsystem.  It'd be the easiest to route all
> through -mm but the conversion patches can go through individual
> subsystem trees afterwards if necessary.

But you're working on other code which will depend on this?  If so
perhaps these should be held in your tree.
--
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/