From: Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sebastian Andrzej Siewior
<sebastian-E0PNVn5OA6ohrxcnuTQ+TQ@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [git pull] ioapic-cleanups-for-v3.9
Date: Fri, 25 Jan 2013 11:49:15 +0100 [thread overview]
Message-ID: <20130125104915.GB23332@gmail.com> (raw)
In-Reply-To: <20130125100040.GA13908-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
* Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org> wrote:
> Hi Ingo,
>
> The following changes since commit 7d1f9aeff1ee4a20b1aeb377dd0f579fe9647619:
>
> Linux 3.8-rc4 (2013-01-17 19:25:45 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/ioapic-cleanups-for-v3.9
Hm, there are some not so trivial looking conflicts in
io_apic.c, due to the MSI patches I applied yesterday:
5ca72c4f7c41 AHCI: Support multiple MSIs
08261d87f7d1 PCI/MSI: Enable multiple MSIs with pci_enable_msi_block_auto()
51906e779f2b x86/MSI: Support multiple MSIs in presense of IRQ remapping
Could you please resolve them and resend?
Thanks,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] ioapic-cleanups-for-v3.9
Date: Fri, 25 Jan 2013 11:49:15 +0100 [thread overview]
Message-ID: <20130125104915.GB23332@gmail.com> (raw)
In-Reply-To: <20130125100040.GA13908@8bytes.org>
* Joerg Roedel <joro@8bytes.org> wrote:
> Hi Ingo,
>
> The following changes since commit 7d1f9aeff1ee4a20b1aeb377dd0f579fe9647619:
>
> Linux 3.8-rc4 (2013-01-17 19:25:45 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/ioapic-cleanups-for-v3.9
Hm, there are some not so trivial looking conflicts in
io_apic.c, due to the MSI patches I applied yesterday:
5ca72c4f7c41 AHCI: Support multiple MSIs
08261d87f7d1 PCI/MSI: Enable multiple MSIs with pci_enable_msi_block_auto()
51906e779f2b x86/MSI: Support multiple MSIs in presense of IRQ remapping
Could you please resolve them and resend?
Thanks,
Ingo
next prev parent reply other threads:[~2013-01-25 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 10:00 [git pull] ioapic-cleanups-for-v3.9 Joerg Roedel
2013-01-25 10:00 ` Joerg Roedel
[not found] ` <20130125100040.GA13908-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2013-01-25 10:49 ` Ingo Molnar [this message]
2013-01-25 10:49 ` Ingo Molnar
[not found] ` <20130125104915.GB23332-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-25 11:31 ` Joerg Roedel
2013-01-25 11:31 ` Joerg Roedel
2013-01-28 15:58 ` Joerg Roedel
2013-01-28 15:58 ` Joerg Roedel
[not found] ` <20130128155757.GA3643-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2013-01-29 9:07 ` Ingo Molnar
2013-01-29 9:07 ` 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=20130125104915.GB23332@gmail.com \
--to=mingo-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sebastian-E0PNVn5OA6ohrxcnuTQ+TQ@public.gmane.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 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.