linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Will Deacon <Will.Deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	alvise rigo <a.rigo@virtualopensystems.com>
Subject: Re: [PATCH] pci: generic host: make it more generic
Date: Tue, 11 Nov 2014 18:24:18 +0000	[thread overview]
Message-ID: <20141111182418.GA5507@red-moon> (raw)
In-Reply-To: <CACVXFVNAc9axtESmo1zGZ3GMquTzjzWR3jx-b3tbhhLfQDDRcg@mail.gmail.com>

On Tue, Nov 11, 2014 at 02:02:20PM +0000, Ming Lei wrote:

[...]

> > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/296535.html
> >
> > Patch above is already queued and applies most of the changes you have posted
> > above.
> 
> I should have looked at list first before writing the patch, :-(
> 
> Could you make it more generic so that other ARCHs(at least ARM64)
> can benefit from it too?

That's our current goal, we are carrying out clean-ups to remove arch
dependency and move code to the generic layer PCI layer.

Lorenzo

  reply	other threads:[~2014-11-11 18:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 10:33 [PATCH] pci: generic host: make it more generic Ming Lei
2014-11-11 12:29 ` Lorenzo Pieralisi
2014-11-11 14:02   ` Ming Lei
2014-11-11 18:24     ` Lorenzo Pieralisi [this message]
2014-11-12  2:12       ` Ming Lei
2014-11-12  2:47         ` Bjorn Helgaas
2014-11-12  8:58           ` Ming Lei
2014-11-13  3:58             ` Bjorn Helgaas
2014-11-12  9:58         ` Lorenzo Pieralisi
2014-11-12 10:51           ` Ming Lei
2014-11-12 12:32             ` Lorenzo Pieralisi
2014-11-13  1:56               ` Ming Lei
2015-01-15 11:10 ` Alexander Graf

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=20141111182418.GA5507@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=a.rigo@virtualopensystems.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).