mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
	Zachary Amsden <zach@vmware.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] x86: APIC: Remove apic_write_around(); use alternatives
Date: Sat, 19 Jul 2008 23:53:25 +0200	[thread overview]
Message-ID: <20080719215325.GA12737@elte.hu> (raw)
In-Reply-To: <20080719214944.GC836@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> > > maciej, patch will go first, and x2apic will goes later, so bisect 
> > > on x2apic will be broken.
> > 
> > hm, ok. Ingo? should I send the rebased 30 or so patches. or we can 
> > move this patch later.
> 
> hm, yes, please send the rebased patches - as this stuff has some 
> risks so bisectability is important.

hm, actually - the order is correct so no need to rebase any of this.

We've got two topics: tip/x86/apic and tip/x86/x2apic.

both tip/x86/x2apic and tip/x86/apic were OK standalone. I merged them 
together in this commit:

commit 453c1404c5273a30d715e5a83372a78cff70b6d9
Merge: a208f37... 35b6805...
Author: Ingo Molnar <mingo@elte.hu>
Date:   Fri Jul 18 23:00:05 2008 +0200

    Merge branch 'x86/apic' into x86/x2apic

    Conflicts:

        arch/x86/kernel/paravirt.c
        arch/x86/kernel/smpboot.c
        arch/x86/kernel/vmi_32.c
        arch/x86/lguest/boot.c
        arch/x86/xen/enlighten.c
        include/asm-x86/apic.h
        include/asm-x86/paravirt.h

    Signed-off-by: Ingo Molnar <mingo@elte.hu>

and that didnt work straight away, so i applied your fixups - but that's 
the next commit. So there's only a single commit that is not bisectable 
and that's OK.

so unless there's some other breakage i missed, this should be fine and 
no need to resend/rebase anything.

	Ingo

  reply	other threads:[~2008-07-19 21:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 18:15 Maciej W. Rozycki
2008-07-18 10:52 ` Ingo Molnar
2008-07-18 16:25   ` Yinghai Lu
2008-07-18 17:01     ` Yinghai Lu
2008-07-18 21:03       ` Ingo Molnar
2008-07-18 21:13         ` Yinghai Lu
2008-07-18 22:02           ` Maciej W. Rozycki
2008-07-18 22:42             ` Zachary Amsden
2008-07-18 22:49               ` Suresh Siddha
2008-07-18 22:51                 ` Yinghai Lu
2008-07-18 23:00                   ` Suresh Siddha
2008-07-18 23:04                     ` Yinghai Lu
2008-07-18 23:18                       ` Suresh Siddha
2008-07-19 21:49                         ` Ingo Molnar
2008-07-19 21:53                           ` Ingo Molnar [this message]
2008-07-20 12:08                             ` Ingo Molnar
2008-07-20 15:04                               ` Ingo Molnar
2008-07-21 17:59                               ` Suresh Siddha
2008-07-22 13:24                                 ` Yong Wang
2008-07-22 13:48                                   ` Ingo Molnar
2008-07-18 23:43                 ` Zachary Amsden
2008-07-19 21:43                   ` Ingo Molnar
2008-07-18 22:58         ` Suresh Siddha
2008-07-19 21:47           ` Ingo Molnar

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=20080719215325.GA12737@elte.hu \
    --to=mingo@elte.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.com \
    --cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome