From: Hugh Dickins <hugh@veritas.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip] x86: include inverse Xmas tree patches
Date: Sat, 28 Mar 2009 15:17:13 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0903281508410.21235@blonde.anvils> (raw)
In-Reply-To: <1238251730.2526.2.camel@ht.satnam>
On Sat, 28 Mar 2009, Jaswinder Singh Rajput wrote:
> The following changes since commit 29219683c46cb89edf5c58418b5305b14646d030:
> Ingo Molnar (1):
> Merge branches 'x86/apic', 'x86/cleanups', 'x86/mm', 'x86/pat', 'x86/setup' and 'x86/signal'; commit 'v2.6.29' into x86/core
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-Xmas.git x86/core
>
> Jaswinder Singh Rajput (49):
> x86: process_32.c include inverse Xmas tree effect
> x86: signal.c include inverse Xmas tree effect
> x86: entry_32.S include inverse Xmas tree effect
> x86: traps.c include inverse Xmas tree effect
> x86: irq.c include inverse Xmas tree effect
> x86: irq_32.c include inverse Xmas tree effect
> x86: dumpstack.c include inverse Xmas tree effect
> x86: time_32.c include inverse Xmas tree effect
> x86: ioport.c include inverse Xmas tree effect
> x86: ldt.c include inverse Xmas tree effect
> x86: dumpstack_32.c include inverse Xmas tree effect
> x86: setup.c include inverse Xmas tree effect
> x86: i8259.c include inverse Xmas tree effect
> x86: irqinit_32.c include inverse Xmas tree effect
> x86: probe_roms_32.c include inverse Xmas tree effect
> x86: sys_i386_32.c include inverse Xmas tree effect
> x86: i386_ksyms_32.c include inverse Xmas tree effect
> x86: bootflag.c include inverse Xmas tree effect
> x86: e820.c include inverse Xmas tree effect
> x86: pci-dma.c include inverse Xmas tree effect
> x86: quirks.c include inverse Xmas tree effect
> x86: i8237.c include inverse Xmas tree effect
> x86: alternative.c include inverse Xmas tree effect
> x86: tsc.c include inverse Xmas tree effect
> x86: process.c include inverse Xmas tree effect
> x86: xsave.c include inverse Xmas tree effect
> x86: ptrace.c include inverse Xmas tree effect
> x86: ds.c include inverse Xmas tree effect
> x86: tls.c include inverse Xmas tree effect
> x86: step.c include inverse Xmas tree effect
> x86: stacktrace.c include inverse Xmas tree effect
> x86: reboot.c include inverse Xmas tree effect
> x86: msr.c include inverse Xmas tree effect
> x86: cpuid.c include inverse Xmas tree effect
> x86: early-quirks.c include inverse Xmas tree effect
> x86: smp.c include inverse Xmas tree effect
> x86: smpboot.c include inverse Xmas tree effect
> x86: tsc_sync.c include inverse Xmas tree effect
> x86: setup_percpu.c include inverse Xmas tree effect
> x86: trampoline_32.S include inverse Xmas tree effect
> x86: mpparse.c include inverse Xmas tree effect
> x86: module_32.c include inverse Xmas tree effect
> x86: doublefault_32.c include inverse Xmas tree effect
> x86: vm86_32.c include inverse Xmas tree effect
> ix86: early_printk.c include inverse Xmas tree effect
> x86: pcspeaker.c include inverse Xmas tree effect
> x86: head_32.c include inverse Xmas tree effect
> x86: head.c include inverse Xmas tree effect
> x86: init_task.c include inverse Xmas tree effect
Gasp.
Please find a better use for your time.
Imagine, there might be developers out there with real work
to do in these files: all you are doing is throwing silly
little obstacles in their way.
IMHO
Hugh
[snip most of it to leave one example]
> --- a/arch/x86/kernel/alternative.c
> +++ b/arch/x86/kernel/alternative.c
> @@ -1,17 +1,18 @@
> +#include <linux/kprobes.h>
> +#include <linux/vmalloc.h>
> #include <linux/module.h>
> -#include <linux/sched.h>
> #include <linux/mutex.h>
> +#include <linux/sched.h>
> #include <linux/list.h>
> -#include <linux/kprobes.h>
> #include <linux/mm.h>
> -#include <linux/vmalloc.h>
> +
> #include <asm/alternative.h>
> +#include <asm/cacheflush.h>
> #include <asm/sections.h>
> +#include <asm/vsyscall.h>
> #include <asm/pgtable.h>
> #include <asm/mce.h>
> #include <asm/nmi.h>
> -#include <asm/vsyscall.h>
> -#include <asm/cacheflush.h>
> #include <asm/io.h>
>
> #define MAX_PATCH_LEN (255-1)
next prev parent reply other threads:[~2009-03-28 15:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 14:48 Jaswinder Singh Rajput
2009-03-28 15:07 ` Joerg Roedel
2009-03-28 16:48 ` Jaswinder Singh Rajput
2009-03-28 17:16 ` Jaswinder Singh Rajput
2009-03-28 15:07 ` Alexey Dobriyan
2009-03-28 15:55 ` Alan Cox
2009-03-28 15:58 ` Alexey Dobriyan
2009-03-28 16:11 ` Jaswinder Singh Rajput
2009-03-28 16:28 ` Alan Cox
2009-03-28 19:03 ` Sam Ravnborg
2009-03-28 22:25 ` H. Peter Anvin
2009-03-28 22:37 ` Al Viro
2009-03-28 23:31 ` Thomas Gleixner
2009-03-28 23:34 ` Ingo Molnar
2009-03-28 23:39 ` Thomas Gleixner
2009-03-29 0:00 ` Ingo Molnar
2009-03-29 0:24 ` Al Viro
2009-03-29 10:25 ` Alexey Dobriyan
2009-03-29 0:28 ` Thomas Gleixner
2009-03-29 1:58 ` Ingo Molnar
2009-03-29 7:57 ` Jaswinder Singh Rajput
2009-03-28 15:17 ` Hugh Dickins [this message]
2009-03-28 23:40 ` Ingo Molnar
2009-03-29 6:38 ` Jaswinder Singh Rajput
2009-03-29 11:46 ` Thomas Gleixner
2009-03-29 14:38 ` Jaswinder Singh Rajput
2009-03-28 23:35 ` Ingo Molnar
2009-03-29 5:54 ` Jaswinder Singh Rajput
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0903281508410.21235@blonde.anvils \
--to=hugh@veritas.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®