linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>, linux-pci@vger.kernel.org
Subject: Re: PCI tree
Date: Wed, 05 Sep 2012 21:08:39 -0700	[thread overview]
Message-ID: <504821C7.1030005@xenotime.net> (raw)
In-Reply-To: <20120905204539.7ea93350@nehalam.linuxnetplumber.net>

On 09/05/2012 08:45 PM, Stephen Hemminger wrote:

> Where is current PCI upstream tree.
> I thought it was
>  git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci 
> But this is still back at 3.3.6 from March.
> --


MAINTAINERS file says:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git

Jesse is no longer the PCI maintainer.


-- 
~Randy

      reply	other threads:[~2012-09-06  4:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  3:45 PCI tree Stephen Hemminger
2012-09-06  4:08 ` Randy Dunlap [this message]

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=504821C7.1030005@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /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).