From: Denis Bolotin <dbolotin@marvell.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <aelior@marvell.com>, Denis Bolotin <dbolotin@marvell.com>
Subject: [PATCH net 0/2] qed: Misc fixes in qed
Date: Thu, 3 Jan 2019 12:02:38 +0200 [thread overview]
Message-ID: <20190103100240.17534-1-dbolotin@marvell.com> (raw)
Hi Dave,
This patch series fixes 2 potential bugs in qed.
Please consider applying to net.
Thanks,
Denis
Denis Bolotin (2):
qed: Fix qed_chain_set_prod() for PBL chains with non power of 2 page
count
qed: Fix qed_ll2_post_rx_buffer_notify_fw() by adding a write memory
barrier
drivers/net/ethernet/qlogic/qed/qed_ll2.c | 4 ++++
include/linux/qed/qed_chain.h | 31 +++++++++++++++++++++++++++++++
2 files changed, 35 insertions(+)
--
1.8.3.1
next reply other threads:[~2019-01-03 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 10:02 Denis Bolotin [this message]
2019-01-03 10:02 ` [PATCH net 1/2] qed: Fix qed_chain_set_prod() for PBL chains with non power of 2 page count Denis Bolotin
2019-01-03 10:02 ` [PATCH net 2/2] qed: Fix qed_ll2_post_rx_buffer_notify_fw() by adding a write memory barrier Denis Bolotin
2019-01-04 20:57 ` [PATCH net 0/2] qed: Misc fixes in qed David Miller
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=20190103100240.17534-1-dbolotin@marvell.com \
--to=dbolotin@marvell.com \
--cc=aelior@marvell.com \
--cc=davem@davemloft.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).