From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: currently missing kernel devel trees
Date: Thu, 13 Oct 2011 14:35:44 -0400 [thread overview]
Message-ID: <20111013183543.GI15499@phenom.oracle.com> (raw)
In-Reply-To: <20111013174358.b20fedb97c7b53db2ba82ff6@canb.auug.org.au>
> swiotlb
> ibft
I don't have anything yet there for 3.2, but was going to resurrect those
trees once my GPG key got enough signatures to send it to hpa for kernel.org
access.
next prev parent reply other threads:[~2011-10-13 18:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 6:43 currently missing kernel devel trees Stephen Rothwell
2011-10-13 11:26 ` Josh Boyer
2011-10-13 12:36 ` Dave Airlie
2011-10-13 13:33 ` Stephen Rothwell
2011-10-13 13:53 ` Dave Airlie
2011-10-13 13:54 ` Stephen Rothwell
2011-10-13 15:15 ` Bob Copeland
2011-10-13 23:00 ` Stephen Rothwell
2011-10-13 18:35 ` Konrad Rzeszutek Wilk [this message]
2011-10-14 0:21 ` Randy Dunlap
2011-10-14 0:33 ` Stephen Rothwell
2011-10-14 1:03 ` Phillip Lougher
2011-10-24 9:20 ` Stephen Rothwell
2011-11-02 17:32 ` Phillip Lougher
2011-11-03 1:18 ` Stephen Rothwell
2011-10-14 3:25 ` Mike Frysinger
2011-10-15 17:57 ` Mike Frysinger
2011-10-24 9:38 ` Stephen Rothwell
2011-10-16 21:11 ` Wim Van Sebroeck
2011-10-24 9:50 ` Stephen Rothwell
2011-10-25 18:52 ` Wim Van Sebroeck
2012-03-15 20:32 ` Change of the linux-watchdog-next tree location Wim Van Sebroeck
2012-03-15 22:06 ` Stephen Rothwell
2011-10-26 20:45 ` currently missing kernel devel trees David Teigland
2011-10-29 6:50 ` Stephen Rothwell
2011-10-28 2:58 ` Guan Xuetao
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=20111013183543.GI15499@phenom.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).