From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ram Pai <linuxram@us.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
yinghai@kernel.org, bhutchings@solarflare.com,
socketcan@hartkopp.net, bhelgaas@google.com,
linux@dominikbrodowski.net
Subject: Re: [PATCH 0/5 v2] PCI: fix cardbus and sriov regressions
Date: Wed, 6 Jul 2011 10:46:48 -0700 [thread overview]
Message-ID: <20110706104648.312ba4c7@jbarnes-desktop> (raw)
In-Reply-To: <20110706085316.GA3543@ram-ThinkPad-T61>
On Wed, 6 Jul 2011 01:53:16 -0700
Ram Pai <linuxram@us.ibm.com> wrote:
> On Sun, Jul 03, 2011 at 02:30:00PM -0700, Linus Torvalds wrote:
> > and I'd really change the function argument to take that kind of
> > simplified thing instead.
> >
> > And that cleanup/re-organization would be prime material for a totally
> > independent patch that changes no semantics at all, just prepares for
> > the other changes.
> >
> > That way the final "patch 2" would be smaller and do the semantic
> > changes, instead of being a mix of semantic changes and infrastructure
> > changes.
> >
> > And some of the cleanup stuff I could merge for 3.0 just to make things easier.
> >
> > Hmm?
>
> Here is a cleaned up patch that just adds functionality to kernel/resource.c
> It does make a small semantic addition to allocate_resource(), where it reallocates
> the resource with a newer size if that resource was already allocated.
>
> Will this be acceptable for 3.0.0?
Up to Linus, I have no problem with the patch though, it seems like a
good cleanup and is good to keep separate from the other patches. Once
it lands I can queue up the dependent patches in -next.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2011-07-06 17:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 23:47 [PATCH 0/5 v2] PCI: fix cardbus and sriov regressions Ram Pai
2011-06-30 23:47 ` [PATCH 1/5 v2] PCI: honor child buses optional size in hot plug configuration Ram Pai
2011-06-30 23:47 ` [PATCH 2/5 v2] PCI : ability to relocate assigned pci-resources Ram Pai
2011-06-30 23:47 ` [PATCH 3/5 v2] PCI: make SRIOV resources optional Ram Pai
2011-07-01 6:01 ` Oliver Hartkopp
2011-07-06 17:48 ` Jesse Barnes
2011-07-07 15:34 ` Oliver Hartkopp
2011-06-30 23:47 ` [PATCH 4/5 v2] PCI: make cardbus-bridge " Ram Pai
2011-06-30 23:47 ` [PATCH 5/5 v2] PCI: code and terminology cleanup Ram Pai
2011-07-01 23:07 ` [PATCH 0/5 v2] PCI: fix cardbus and sriov regressions Ben Hutchings
2011-07-02 13:04 ` Ram Pai
2011-07-04 23:35 ` Ben Hutchings
2011-07-03 21:30 ` Linus Torvalds
2011-07-04 3:55 ` Harry Wei
2011-07-06 8:53 ` Ram Pai
2011-07-06 17:46 ` Jesse Barnes [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=20110706104648.312ba4c7@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=linuxram@us.ibm.com \
--cc=socketcan@hartkopp.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.