public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for October 21
Date: Tue, 21 Oct 2008 18:20:17 +0100	[thread overview]
Message-ID: <1224609617.16910.94.camel@macbook.infradead.org> (raw)
In-Reply-To: <20081021195109.ed83b102.sfr@canb.auug.org.au>

Missing the git://git.infradead.org/iommu-2.6.git tree, which contains a
bunch of patches which had got dropped over the last few weeks, and
which I need to send to Linus before the merge window closes. I was
really hoping they'd be in today's linux-next :(

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel•com                              Intel Corporation

  parent reply	other threads:[~2008-10-21 17:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21  8:51 linux-next: Tree for October 21 Stephen Rothwell
2008-10-21 12:07 ` Josh Boyer
2008-10-21 12:14   ` Stephen Rothwell
2008-10-21 13:02     ` Josh Boyer
2008-10-21 17:20 ` David Woodhouse [this message]
2008-10-21 22:55   ` Stephen Rothwell
2008-10-22  4:25 ` linux-next: Tree for October 21 (jffs2) Randy Dunlap
2008-10-22  4:47 ` linux-next: Tree for October 21 (staging/prism2-usb) Randy Dunlap
2008-10-22  4:59   ` Greg KH
2008-10-22  5:05     ` Randy Dunlap
2008-10-22  4:57 ` linux-next: Tree for October 21 (printk format warnings) Randy Dunlap
2008-10-22  5:01   ` Greg KH
2008-10-22  5:07     ` David Miller
2008-10-22  5:11       ` Randy Dunlap
2008-10-22  5:20         ` David Miller
2008-10-22  5:09     ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2010-10-21  4:15 linux-next: Tree for October 21 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=1224609617.16910.94.camel@macbook.infradead.org \
    --to=dwmw2@infradead$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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