All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Venki Pallipadi <venkatesh.pallipadi@intel.com>,
	"Brown, Len" <len.brown@intel.com>
Subject: Re: [PATCH] idle (arch, acpi and apm) and lockdep
Date: Fri, 25 Apr 2008 20:19:50 +0200	[thread overview]
Message-ID: <1209147590.1956.12.camel@lappy> (raw)
In-Reply-To: <dd18b0c30804251108q2d55736dtd4807db2a9ffb6c5@mail.gmail.com>

On Fri, 2008-04-25 at 18:08 +0000, Justin Mattock wrote:
> O.K. I applied this patch, below are the results:

> patching file arch/x86/kernel/process_32.c
> Hunk #1 FAILED at 111.
> Hunk #2 FAILED at 126.
> Hunk #3 FAILED at 183.
> Hunk #4 FAILED at 194.
> 4 out of 4 hunks FAILED -- saving rejects to file
> arch/x86/kernel/process_32.c.rej
> patching file arch/x86/kernel/process_64.c
> Hunk #1 FAILED at 106.
> Hunk #2 FAILED at 179.
> 2 out of 2 hunks FAILED -- saving rejects to file
> arch/x86/kernel/process_64.c.rej
> patching file drivers/acpi/processor_idle.c
> Hunk #1 FAILED at 418.
> Hunk #2 FAILED at 519.
> Hunk #3 FAILED at 535.
> 3 out of 3 FAILED -- saving rejects to file drivers/acpi/processor_idle.c.rej
> pathing file arch/x86/kernel/apm_32.c
> Hunk #1 FAILED at 904.
> Hunk #2 FAILED at 912.
> 2 out of 2 hunks FAILED -- saving rejects to file arch/x86/kernel/apm_32.c.rej
> patching file include/asm/asm-x86/processor.h
> Hunk #1 FAILED at 723.
> 1 out of 1 hunk FAILE -- saving rejects to file include/asm-x86/processor.h.rej
> patching file arch/x86/kernel/process.c
> Hunk #2 succeeded at 44 with fuzz 2.
> 
> When I compile the kernel I'm receiving this.
> 
> arch/x86/kernel/process.o: In function `select_idle_routine':
> process.c:(.cpuinit.text+0x0): multiple definition of `select_idle_routine'
> arch/x86/kernel/process_32.o:process_32.c(.cpuinit.text+0x0: first defined here
> arch/x86/kernel/process.o: In function `cpu_idle_wait':
> process.c:(text+0x16): multiple definition of `cpu_idle_wait'
> arch/x86/kernel/process_32.o:process_32.c:(.text0x432): first defined here
> arch/x86/kernel/process.o: In function `mwait_idle_with_hints':
> process.c:(.text+0x113): multiple definition of 'mwait_idle_with_hints'
> arch/x86/kernel/process_32.o:process_32.c:(.text+0x1db): first defined here
> make[1]: *** [arch/x86/kernel/built-in.o] Error 1
> make: *** [arch/x86/kernel] Error 2
> 
> 
> Should I just go ahead and try git-pull to see if these patches are
> applied over there correctly.
> regards;

That's no good :-/

weird, I have:

# git describe
v2.6.25-4569-gb69d398

# quilt push
Applying patch patches/idle-lockdep-1.patch
patching file arch/x86/kernel/process_32.c
patching file arch/x86/kernel/process_64.c
patching file drivers/acpi/processor_idle.c
patching file arch/x86/kernel/apm_32.c
patching file include/asm-x86/processor.h
patching file arch/x86/kernel/process.c

Now at patch patches/idle-lockdep-1.patch


And I did a i386 and x86_64 defconfig build before I send it out.


  reply	other threads:[~2008-04-25 18:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25  0:24 [ INFO: iconsistent lock state ] Justin Mattock
2008-04-25 12:11 ` Peter Zijlstra
2008-04-25 14:47   ` Justin Mattock
2008-04-25 14:59     ` Peter Zijlstra
2008-04-25 15:39       ` [PATCH] idle (arch, acpi and apm) and lockdep Peter Zijlstra
2008-04-25 18:08         ` Justin Mattock
2008-04-25 18:19           ` Peter Zijlstra [this message]
2008-04-25 19:18             ` Justin Mattock
2008-04-25 22:05               ` Justin Mattock
2008-04-25 15:45       ` [ INFO: iconsistent lock state ] Justin Mattock

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=1209147590.1956.12.camel@lappy \
    --to=peterz@infradead.org \
    --cc=justinmattock@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=venkatesh.pallipadi@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.