From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Alex Chiang <achiang@hp.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH 1/9] pci: add pci_bridge_release_resources and pci_bus_release__bridge_resources
Date: Mon, 8 Feb 2010 11:22:57 -0800 [thread overview]
Message-ID: <20100208112257.1cd54302@jbarnes-piketon> (raw)
In-Reply-To: <1264150948-9052-2-git-send-email-yinghai@kernel.org>
On Fri, 22 Jan 2010 01:02:20 -0800
Yinghai Lu <yinghai@kernel.org> wrote:
> so later we could use it to release small resource before pci assign
> unassign res
>
> -v2: change name to release_child_resources according to Jesse
> -v3: according to Linus, move release_child_resources to resource.c
> also need to put the lock around them all to avoid recursive
> deep. (my test case only have one level that need to be released)
> -v4: seperate release_child_resources to another patch
> according to Bjorn, change hard code 3 to PCI_BRIDGE_RESOURCE_END
> -v5: remove unused in the name, and also use enum for release type
> according to Jesse
> -v6: use pci_is_root_bus instead according to Alex.
> -v7: remove the switch case in pci_bus_release_resources accord to
> Alex -v8: change some comments and style according to Alex again
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> Reviewed-by: Alex Chiang <achiang@hp.com>
> ---
Applied this series finally, thanks Yinghai for all your work
responding to the feedback. Let's hope it doesn't break too many
things in 2.6.34!
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-02-08 19:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 9:02 [PATCH -v19 0/9] pci: update pci bridge resources Yinghai Lu
2010-01-22 9:02 ` [PATCH 1/9] pci: add pci_bridge_release_resources and pci_bus_release__bridge_resources Yinghai Lu
2010-02-08 19:22 ` Jesse Barnes [this message]
2010-01-22 9:02 ` [PATCH 2/9] pci: add failed_list to record failed one for pci_bus_assign_resources Yinghai Lu
2010-01-22 9:02 ` [PATCH 3/9] pci: reject mmio range start from 0 on pci_bridge read Yinghai Lu
2010-01-22 9:02 ` [PATCH 4/9] pci: don't shrink bridge resources Yinghai Lu
2010-01-22 9:02 ` [PATCH 5/9] pci: update bridge res to get more big range in pci assign unssign Yinghai Lu
2010-01-22 9:02 ` [PATCH 6/9] pci: introduce pci_assign_unassigned_bridge_resources Yinghai Lu
2010-01-22 9:02 ` [PATCH 7/9] pci: pciehp clean flow in pciehp_configure_device Yinghai Lu
2010-01-22 9:02 ` [PATCH 8/9] pci: pciehp second try to get big range for pcie devices Yinghai Lu
2010-01-22 9:02 ` [PATCH 9/9] pci: set PCI_PREF_RANGE_TYPE_64 in pci_bridge_check_ranges Yinghai Lu
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=20100208112257.1cd54302@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=achiang@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=ink@jurassic.park.msu.ru \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®