From: Ingo Molnar <mingo@elte.hu>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: intel-iommu: Add for_each_iommu() and for_each_active_iommu() macros
Date: Wed, 8 Apr 2009 13:00:37 +0200 [thread overview]
Message-ID: <20090408110037.GD17321@elte.hu> (raw)
In-Reply-To: <1239066583.22733.258.camel@macbook.infradead.org>
* David Woodhouse <dwmw2@infradead.org> wrote:
> On Mon, 2009-04-06 at 17:59 -0700, Andrew Morton wrote:
> >
> > Three days old? Never been in linux-next afaict.
> >
> > Please don't do that.
>
> Sorry about that. There was some confusion about whether it was
> going via Ingo's or my tree, and it ended up in neither. It
> depended on certain things in Ingo's tree, so I couldn't easily
> add it to my tree any earlier.
Well, they could have ended up in the x86 tree or in the IOMMU tree,
but the patches were all very late and went through various review
rounds with me so they had no chance to end up there in a finished
state before the merge window.
I didnt mind you pushing them to Linus separately and gave an
Acked-by for the bits and for that merge route, but all the usual
protocols still have to be followed if you do that: review, testing,
proper exposure.
Ingo
next prev parent reply other threads:[~2009-04-08 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904062159.n36Lx1OJ001967@hera.kernel.org>
2009-04-07 0:59 ` intel-iommu: Add for_each_iommu() and for_each_active_iommu() macros Andrew Morton
2009-04-07 1:09 ` David Woodhouse
2009-04-07 1:19 ` David Woodhouse
2009-04-07 1:24 ` Andrew Morton
2009-04-07 1:29 ` Steven Rostedt
2009-04-07 2:58 ` David Woodhouse
2009-04-07 3:02 ` Steven Rostedt
2009-04-07 3:29 ` David Woodhouse
2009-04-08 11:00 ` Ingo Molnar [this message]
2009-04-09 0:42 ` David Woodhouse
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=20090408110037.GD17321@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.