From: Jon Mason <jon.mason@intel.com>
To: linux-kernel@vger.kernel.org
Cc: Dave Jiang <dave.jiang@intel.com>
Subject: [PATCH 0/10] NTB: Bug Fixes
Date: Mon, 6 May 2013 18:55:19 -0700 [thread overview]
Message-ID: <1367891729-11738-1-git-send-email-jon.mason@intel.com> (raw)
This series of patches contains a number of bug fixes for the PCI-E Non-Transparent Bridge (NTB) device driver.
Some of these patches have been posted to LKML before, but I wanted all to be available for review prior to sending a pull request.
Thanks,
Jon
Dan Carpenter (2):
ntb: off by one sanity checks
NTB: fix pointer math issues
Jon Mason (8):
NTB: variable dereferenced before check
NTB: Handle 64bit BAR sizes
NTB: Link toggle memory leak
NTB: reset tx_index on link toggle
NTB: Correctly handle receive buffers of the minimal size
NTB: memcpy lockup workaround
ntb_netdev: remove from list on exit
NTB: Multiple NTB client fix
drivers/net/ntb_netdev.c | 2 +
drivers/ntb/ntb_hw.c | 10 +--
drivers/ntb/ntb_transport.c | 175 ++++++++++++++++++++++++++++---------------
3 files changed, 121 insertions(+), 66 deletions(-)
next reply other threads:[~2013-05-07 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 1:55 Jon Mason [this message]
2013-05-07 1:55 ` [PATCH 01/10] NTB: variable dereferenced before check Jon Mason
2013-05-07 1:55 ` [PATCH 02/10] ntb: off by one sanity checks Jon Mason
2013-05-07 1:55 ` [PATCH 03/10] NTB: fix pointer math issues Jon Mason
2013-05-07 1:55 ` [PATCH 04/10] NTB: Handle 64bit BAR sizes Jon Mason
2013-05-07 1:55 ` [PATCH 05/10] NTB: Link toggle memory leak Jon Mason
2013-05-07 1:55 ` [PATCH 06/10] NTB: reset tx_index on link toggle Jon Mason
2013-05-07 1:55 ` [PATCH 07/10] NTB: Correctly handle receive buffers of the minimal size Jon Mason
2013-05-07 1:55 ` [PATCH 08/10] NTB: memcpy lockup workaround Jon Mason
2013-05-07 1:55 ` [PATCH 09/10] ntb_netdev: remove from list on exit Jon Mason
2013-05-07 1:55 ` [PATCH 10/10] NTB: Multiple NTB client fix 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=1367891729-11738-1-git-send-email-jon.mason@intel.com \
--to=jon.mason@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-kernel@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