From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-next@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: linux-next: manual merge of the iommu tree
Date: Mon, 29 Dec 2008 23:20:02 +1100 [thread overview]
Message-ID: <20081229232002.cd7aa33d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081229121501.GE9628@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 377 bytes --]
Hi Ingo,
On Mon, 29 Dec 2008 13:15:01 +0100 Ingo Molnar <mingo@elte.hu> wrote:
>
> had a resolution for this cached from tip/master - so i just re-integrated
> and re-pushed auto-iommu-next so it should go away next time you pick it
> up. Thanks,
Thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-29 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 12:04 linux-next: manual merge of the iommu tree Stephen Rothwell
2008-12-29 12:15 ` Ingo Molnar
2008-12-29 12:20 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-29 12:10 Stephen Rothwell
2009-01-06 5:57 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=20081229232002.cd7aa33d.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arjan@infradead.org \
--cc=jeremy@goop.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
/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