This patch-set will cleanup and refine the code related to scheduler and
save few lines.

Rough tested (random benchmark) with latest tip/master on a desktop.

Michael Wang (11):
        [PATCH 01/11] sched/cleanup: remove the extra line in 
init_sched_fair_class()
        [PATCH 02/11] sched/cleanup: remove the extra parm of 
alloc_thread_info_node()
        [PATCH 03/11] sched/cleanup: remove the extra parm of copy_flags()
        [PATCH 04/11] sched/cleanup: refine rt_policy()
        [PATCH 05/11] sched/cleanup: remove the extra parm of wakeup_gran()
        [PATCH 06/11] sched/cleanup: refine __setup_irq()
        [PATCH 07/11] sched/cleanup: remove the extra parm of 
irq_set_thread_affinity()
        [PATCH 08/11] sched/cleanup: remove the extra parm of 
sched_clock_idle_wakeup_event()
        [PATCH 09/11] sched/cleanup: remove the extra parm of 
tick_nohz_start_idle()
        [PATCH 10/11] sched/cleanup: remove the extra parm of 
retrigger_next_event()
        [PATCH 11/11] sched/cleanup: remove the extra parm of find_new_ilb()
---
 b/arch/x86/kernel/tsc.c         |    2 +-
 b/drivers/acpi/processor_idle.c |    4 ++--
 b/include/linux/sched.h         |    7 ++-----
 b/kernel/fork.c                 |    8 +++-----
 b/kernel/hrtimer.c              |    8 ++++----
 b/kernel/irq/internals.h        |    2 +-
 b/kernel/irq/manage.c           |    6 ++----
 b/kernel/irq/migration.c        |    2 +-
 b/kernel/sched/clock.c          |    2 +-
 b/kernel/sched/fair.c           |    1 -
 b/kernel/sched/sched.h          |    4 +---
 b/kernel/time/tick-sched.c      |    2 +-
 kernel/fork.c                   |    4 ++--
 kernel/irq/manage.c             |    7 +++----
 kernel/sched/fair.c             |    8 ++++----
 kernel/time/tick-sched.c        |    4 ++--
 16 files changed, 30 insertions(+), 41 deletions(-)

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

Reply via email to