Re: [guv 04/16] core: Convert __get_cpu_var uses

[Steven Rostedt]

As Tejun said, each commit needs its own change log. Never expect a
change lgo from another commit to be read for changes in this commit.

> Index: linux/kernel/events/callchain.c
> Index: linux/kernel/events/core.c
> Index: linux/kernel/printk/printk.c
> Index: linux/kernel/rcutree.c
> Index: linux/kernel/sched/cputime.c
> Index: linux/kernel/sched/fair.c
> Index: linux/kernel/sched/rt.c
> Index: linux/kernel/time/tick-sched.c
> Index: linux/net/ipv4/syncookies.c
> Index: linux/net/ipv6/syncookies.c
> Index: linux/block/blk-iopoll.c
> Index: linux/block/blk-softirq.c
> Index: linux/fs/fscache/object.c
> Index: linux/include/linux/kernel_stat.h
> Index: linux/include/linux/kprobes.h
> Index: linux/include/linux/percpu.h
> Index: linux/include/net/netfilter/nf_conntrack.h
> Index: linux/kernel/hrtimer.c
> Index: linux/kernel/irq_work.c
> Index: linux/kernel/rcutree_plugin.h
> Index: linux/kernel/sched/clock.c
> Index: linux/kernel/sched/sched.h
> Index: linux/kernel/smp.c
> Index: linux/kernel/softirq.c
> Index: linux/kernel/time/tick-common.c
> Index: linux/kernel/time/tick-oneshot.c
> Index: linux/kernel/trace/ftrace.c
> Index: linux/kernel/user-return-notifier.c
> Index: linux/kernel/watchdog.c
> Index: linux/lib/radix-tree.c
> Index: linux/mm/memcontrol.c
> Index: linux/mm/memory-failure.c
> Index: linux/mm/page-writeback.c
> Index: linux/mm/swap.c
> Index: linux/mm/vmalloc.c
> Index: linux/mm/vmstat.c
> Index: linux/net/core/dev.c
> Index: linux/net/core/drop_monitor.c
> Index: linux/net/core/skbuff.c
> Index: linux/net/ipv4/tcp_output.c
> Index: linux/net/rds/ib_rdma.c
> Index: linux/kernel/timer.c
> Index: linux/kernel/trace/trace.c

This patch needs to be broken up per subsystem. Or are you just looking
for acks from all the maintainers here and you'll pull it in. If that's
the case, you should have Cc'd each of the maintainers of the files that
this touches.

-- Steve

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