public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
	"H. Peter Anvin" <hpa@zytor•com>
Cc: linux-next@vger•kernel.org, David Woodhouse <dwmw2@infradead•org>
Subject: linux-next: manual merge of the x86 tree
Date: Tue, 2 Sep 2008 11:32:10 +1000	[thread overview]
Message-ID: <20080902113210.bc27a75f.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

Hi all,

Today's linux-next merge of the x86 tree got a conflict in
drivers/pci/intel-iommu.c between commit
213f841f903ed16fc1dd29885560cdd159630ed6 ("intel-iommu.c: Blacklist Intel
DG33BU motherboard") from the dwmw2 tree and commit
2ae21010694e56461a63bfc80e960090ce0a5ed9 ("x64, x2apic/intr-remap:
Interrupt remapping infrastructure") from the x86 tree.

I think the easiest thing to do for today is just to revert the change in
the dwmw2 tree and see if you guys can come up with a better patch for
tomorrow.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-09-02  1:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02  1:32 Stephen Rothwell [this message]
2008-09-05 18:22 ` linux-next: manual merge of the x86 tree Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2008-10-14  2:23 Stephen Rothwell
2008-09-11 23:37 Stephen Rothwell
2008-09-14 15:16 ` Ingo Molnar
2008-09-14 18:11   ` Stephen Rothwell
2008-09-11 23:34 Stephen Rothwell
2008-09-14 15:18 ` Ingo Molnar
2008-09-14 18:13   ` Stephen Rothwell
2008-09-03  0:57 Stephen Rothwell
2008-09-05 16:00 ` Ingo Molnar
2008-08-15  3:58 Stephen Rothwell
2008-07-31  2:59 Stephen Rothwell
2008-07-23  2:51 Stephen Rothwell
2008-07-18  2:29 Stephen Rothwell
2008-07-17  1:43 Stephen Rothwell
2008-07-15  2:26 Stephen Rothwell
2008-07-14  1:30 Stephen Rothwell
2008-07-11  1:48 Stephen Rothwell
2008-07-11  1:47 Stephen Rothwell
2008-07-08  0:56 Stephen Rothwell
2008-07-08  3:22 ` Jeremy Fitzhardinge
2008-07-08  5:01   ` Stephen Rothwell
2008-07-08  5:28     ` Jeremy Fitzhardinge
2008-07-08  5:39     ` Ingo Molnar
2008-07-08  0:52 Stephen Rothwell
2008-07-04  3:50 Stephen Rothwell
2008-07-04  3:41 Stephen Rothwell
2008-07-04  9:41 ` Ingo Molnar
2008-06-25  2:28 Stephen Rothwell

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=20080902113210.bc27a75f.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=dwmw2@infradead$(echo .)org \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=tglx@linutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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