linux-kernel - [GIT PULL] NTB bug fixes for v3.18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 18 Oct 2014 12:33:30 -0400
From:	Jon Mason <jdmason@...zu.us>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Dave Jiang <dave.jiang@...el.com>
Subject: [GIT PULL] NTB bug fixes for v3.18

Hi Linus,
Below are a few NTB changes for v3.18. Please consider pulling them.

Thanks,
Jon


The following changes since commit bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9:

  Linux 3.17 (2014-10-05 12:23:04 -0700)

are available in the git repository at:

  git://github.com/jonmason/ntb tags/ntb-3.18

for you to fetch changes up to ab760a0c5667519b375ea9c5ab3a23501c4817ef:

  ntb: Adding split BAR support for Haswell platforms (2014-10-17 07:08:51 -0400)

----------------------------------------------------------------
Add support for Haswell NTB split BARs, a debugfs entry for basic
debugging info, and some code clean-ups.

----------------------------------------------------------------
Dave Jiang (4):
      ntb: move platform detection to separate function
      ntb: conslidate reading of PPD to move platform detection earlier
      ntb: use errata flag set via DID to implement workaround
      ntb: Adding split BAR support for Haswell platforms

Jon Mason (1):
      NTB: debugfs device entry

 drivers/ntb/ntb_hw.c   | 567 +++++++++++++++++++++++++++++++++++++++----------
 drivers/ntb/ntb_hw.h   |  19 +-
 drivers/ntb/ntb_regs.h |  38 +++-
 3 files changed, 501 insertions(+), 123 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/