linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2@ti.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Keystone: PCI: request to pull driver update patches
Date: Tue, 16 Sep 2014 11:53:29 -0400	[thread overview]
Message-ID: <54185CF9.60802@ti.com> (raw)

Hi Bjorn,

Could you please pull the following to your host-keystone (v3.18) branch 
at your earliest convenience if they look good. I have incorporated 
outstanding comments against these patches already.

PCI: keystone: add a pci quirk to limit mrrs
https://patchwork.ozlabs.org/patch/387001/

PCI: keystone: remove handle of PCI mode configuration
https://patchwork.ozlabs.org/patch/387902/

PCI: keystone: read pci device id dynamically to support multiple ports
https://patchwork.ozlabs.org/patch/387905/

As always, thanks in advance for your help!

regards,
-- 
Murali Karicheri
Linux Kernel, Texas Instruments

                 reply	other threads:[~2014-09-16 15:53 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=54185CF9.60802@ti.com \
    --to=m-karicheri2@ti.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).