From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Subject: PCI tree info
Date: Tue, 29 Apr 2008 11:00:08 -0700 [thread overview]
Message-ID: <200804291100.08622.jbarnes@virtuousgeek.org> (raw)
The PCI tree now lives in git:
git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6. There are a
few branches:
for-linus - stuff headed to Linus in the next pull request
linux-next - patches targetted at the following release
master - unmodified Linus upstream branch
I'll try to avoid re-basing, but since the main downstream tree is the PCI
hotplug tree, and Kristen uses quilt, that probably won't be much of an
issue.
If we end up with some big patchsets (like the resource management unification
benh has been talking about) needing a lot of testing, I may create a 'test'
or 'all' branch for akpm and others, but I'll keep everyone posted in that
case.
Thanks,
Jesse
next reply other threads:[~2008-04-29 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 18:00 Jesse Barnes [this message]
2008-04-29 18:27 ` Greg KH
2008-04-29 18:41 ` Jesse Barnes
2008-04-29 23:47 ` Stephen Rothwell
2008-04-30 1:13 ` Jesse Barnes
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=200804291100.08622.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®