linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Feng Kan <fkan@apm.com>, Sasha Levin <sasha.levin@oracle.com>
Subject: [GIT PULL] PCI fixes for v4.0
Date: Thu, 12 Mar 2015 11:20:53 -0500	[thread overview]
Message-ID: <20150312162053.GA20700@google.com> (raw)

Hi Linus,

Here are a couple updates for v4.0.  One fixes a config accessor problem on
APM X-Gene that we introduced when switching to generic config accessors,
and the other fixes an older read-past-end-of-buffer problem in sysfs.

Bjorn


The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:

  Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.0-fixes-2

for you to fetch changes up to 085a68d0010ffa57603b93c2b09fdf98bf74218c:

  PCI: xgene: Add register offset to config space base address (2015-03-05 22:14:21 -0600)

----------------------------------------------------------------
PCI updates for v4.0:

  APM X-Gene host bridge driver
    - Add register offset to config space base address (Feng Kan)

  Miscellaneous
    - Don't read past the end of sysfs "driver_override" buffer (Sasha Levin)

----------------------------------------------------------------
Feng Kan (1):
      PCI: xgene: Add register offset to config space base address

Sasha Levin (1):
      PCI: Don't read past the end of sysfs "driver_override" buffer

 drivers/pci/host/pci-xgene.c | 4 ++--
 drivers/pci/pci-sysfs.c      | 5 +++--
 2 files changed, 5 insertions(+), 4 deletions(-)

             reply	other threads:[~2015-03-12 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 16:20 Bjorn Helgaas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-09 13:26 [GIT PULL] PCI fixes for v4.0 Bjorn Helgaas

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=20150312162053.GA20700@google.com \
    --to=bhelgaas@google.com \
    --cc=fkan@apm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sasha.levin@oracle.com \
    --cc=torvalds@linux-foundation.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).