From: Jon Mason <jdmason@kudzu.us>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-ntb@googlegroups.com
Subject: [GIT PULL] NTB bug fixes for v4.13
Date: Sat, 26 Aug 2017 23:50:14 -0400 [thread overview]
Message-ID: <20170827035014.GA8789@graymalkin.kudzu.us> (raw)
Hello Linus,
Here are a few NTB bug fixes for 4.13. Please consider pulling them.
Thanks,
Jon
The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
are available in the git repository at:
git://github.com/jonmason/ntb tags/ntb-4.13-bugfixes
for you to fetch changes up to 0eb46345364d7318b11068c46e8a68d5dc10f65e:
ntb: ntb_test: ensure the link is up before trying to configure the mws (2017-08-01 15:18:59 -0400)
----------------------------------------------------------------
NTB bug fixes to address an incorrect ntb_mw_count reference in the NTB
transport, improperly bringing down the link if SPADs are corrupted, and
an out-of-order issue regarding link negotiation and data passing.
----------------------------------------------------------------
Dave Jiang (1):
ntb: transport shouldn't disable link due to bogus values in SPADs
Logan Gunthorpe (2):
ntb: use correct mw_count function in ntb_tool and ntb_transport
ntb: ntb_test: ensure the link is up before trying to configure the mws
drivers/ntb/ntb_transport.c | 6 ++----
drivers/ntb/test/ntb_tool.c | 2 +-
tools/testing/selftests/ntb/ntb_test.sh | 4 ++++
3 files changed, 7 insertions(+), 5 deletions(-)
next reply other threads:[~2017-08-27 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 3:50 Jon Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-14 15:54 Jon Mason
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=20170827035014.GA8789@graymalkin.kudzu.us \
--to=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.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
all inboxes | Powered by JetHome®