linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Miller <davem@davemloft.net>, Meelis Roos <mroos@linux.ee>,
	Anatoly Pugachev <matorola@gmail.com>,
	Alex Williamson <alex.williamson@redhat.com>
Subject: [GIT PULL] PCI fixes for v4.7
Date: Thu, 23 Jun 2016 21:36:49 -0500	[thread overview]
Message-ID: <20160624023649.GA14990@localhost> (raw)

Hi Linus,

Here's a small fix for v4.7.  This problem was actually introduced in v4.6
when we unified Kconfig, making PCIe support available everywhere including
sparc, where config reads into unaligned buffers cause warnings.  This fix
is from Dave Miller.

As a reminder, any future PCI fixes for v4.7 will probably come from Alex
Williamson, since I'll be on vacation for most of the rest of this cycle.
I should be back about the time the merge window opens.

Bjorn


The following changes since commit af8c34ce6ae32addda3788d54a7e340cad22516b:

  Linux 4.7-rc2 (2016-06-05 14:31:26 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.7-fixes-1

for you to fetch changes up to ef0dab4aae14e25efddf1577736f8450132800c5:

  PCI: Fix unaligned accesses in VC code (2016-06-20 13:24:20 -0500)

----------------------------------------------------------------
PCI updates for v4.7:

  Miscellaneous
    Fix unaligned accesses in VC code (David Miller)

----------------------------------------------------------------
David Miller (1):
      PCI: Fix unaligned accesses in VC code

 drivers/pci/vc.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

                 reply	other threads:[~2016-06-24  2:36 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=20160624023649.GA14990@localhost \
    --to=helgaas@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matorola@gmail.com \
    --cc=mroos@linux.ee \
    --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).