The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: my bk-pci and bk-driver trees are back up
Date: Mon, 14 Feb 2005 20:24:35 -0800	[thread overview]
Message-ID: <20050215042434.GA19193@kroah.com> (raw)

Could you put my bk-pci and bk-driver trees back into the next -mm
releases?  They are at:

	bk://kernel.bkbits.net/gregkh/linux/pci-2.6
and
	bk://kernel.bkbits.net/gregkh/linux/driver-2.6

Respectively.  I've pluled the 64bit resource stuff out of the pci tree,
that was causing a lot of problems.  It's in a separate bk tree for now
(at: bk://kernel.bkbits.net/gregkh/linux/resource-2.6 if anyone cares).

I've also pulled out the pm changes from my driver tree that were
causing the merge issues before, as I see Pavel has started to split
them up better.

For those who want to see patches of this stuff, big ones can be found
at:

PCI patch:
	http://www.kernel.org/pub/linux/kernel/people/gregkh/pci/2.6/2.6.11-rc3/bk-pci-2.6.11-rc3-mm1.patch
PCI description:
	http://www.kernel.org/pub/linux/kernel/people/gregkh/pci/2.6/2.6.11-rc3/bk-pci-2.6.11-rc3-mm1.patch.desc
	
64bit resource patch:
	http://www.kernel.org/pub/linux/kernel/people/gregkh/pci/2.6/2.6.11-rc3/bk-resource-2.6.11-rc3-mm1.patch
64bit resource description:
	http://www.kernel.org/pub/linux/kernel/people/gregkh/pci/2.6/2.6.11-rc3/bk-resource-2.6.11-rc3-mm1.patch.desc

driver patch:
	http://www.kernel.org/pub/linux/kernel/people/gregkh/driver_core/2.6/2.6.11-rc4/bk-driver-2.6.11-rc4.patch
driver patch description:
	http://www.kernel.org/pub/linux/kernel/people/gregkh/driver_core/2.6/2.6.11-rc4/bk-driver-2.6.11-rc4.patch.desc

thanks,

greg k-h

                 reply	other threads:[~2005-02-15  4:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050215042434.GA19193@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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