mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: "Ian Campbell" <Ian.Campbell@eu.citrix.com>
Cc: "Stefano Stabellini" <Stefano.Stabellini@eu.citrix.com>,
	"jeremy@goop.org" <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen: use PCI interfaces to request IO and MEM resources on platform device.
Date: Tue, 11 Jan 2011 14:10:50 +0000	[thread overview]
Message-ID: <4D2C72FA020000780002BB58@vpn.id2.novell.com> (raw)
In-Reply-To: <1294750884.3831.5866.camel@zakaz.uk.xensource.com>

>>> On 11.01.11 at 14:01, Ian Campbell <Ian.Campbell@eu.citrix.com> wrote:
> The old way was correct circa 2.6.37-rc5 but broken in 2.6.37 final,
> there were a bunch of (reverts of) PCI resource changes in that window,
> If I had to make a guess I'd say it was something in there which did it.

Was it perhaps broken somewhere between -rc5 and -final, but
not in -final itself?

>> I'm mainly asking because if it really addresses some problem,
>> then unmodified_drivers/linux-2.6/platform-pci/platform-pci.c
>> in -unstable should probably get updated too.
> 
> Assuming the pci_* interfaces exist back as far as we care about for
> those drivers then I don't see why not to apply it.

I checked back to .5, where they exist; the question is - how far
back do we care?

Jan


  reply	other threads:[~2011-01-11 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 11:50 Ian Campbell
2011-01-11 12:48 ` [Xen-devel] " Jan Beulich
2011-01-11 13:01   ` Ian Campbell
2011-01-11 14:10     ` Jan Beulich [this message]
2011-01-11 14:18       ` Ian Campbell
2011-01-11 14:27         ` Jan Beulich
2011-01-11 14:33           ` Ian Campbell

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=4D2C72FA020000780002BB58@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.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

all inboxes | Powered by JetHome®