From: Manish Rangankar <manish.rangankar@cavium.com>
To: martin.petersen@oracle.com, lduncan@suse.com, cleech@redhat.com
Cc: linux-scsi@vger.kernel.org, QLogic-Storage-Upstream@cavium.com
Subject: [PATCH 0/7]qedi: Bug fixes.
Date: Fri, 19 May 2017 01:33:14 -0700 [thread overview]
Message-ID: <20170519083321.18030-1-manish.rangankar@cavium.com> (raw)
Martin,
Please apply this patch set to next 'scsi-fixes' series.
Thanks,
Manish
Arun Easi (1):
qedi: Fix bad pte call trace when iscsiuio is stopped.
Manish Rangankar (5):
qedi: Correctly set firmware max supported BDs.
qedi: Set dma_boundary to 0xfff.
qedi: Fix endpoint NULL panic in qedi_set_path.
qedi: Set firmware tcp msl timer value.
qedi: Fix endpoint NULL panic during recovery.
Nilesh Javali (1):
qedi: set max_fin_rt default value
drivers/scsi/qedi/qedi.h | 3 ++-
drivers/scsi/qedi/qedi_fw.c | 2 ++
drivers/scsi/qedi/qedi_iscsi.c | 7 ++++++-
drivers/scsi/qedi/qedi_main.c | 25 +++++++++++++------------
4 files changed, 23 insertions(+), 14 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-05-19 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 8:33 Manish Rangankar [this message]
2017-05-19 8:33 ` [PATCH 1/7] qedi: Fix bad pte call trace when iscsiuio is stopped Manish Rangankar
2017-05-19 8:33 ` [PATCH 2/7] qedi: Correctly set firmware max supported BDs Manish Rangankar
2017-05-19 8:33 ` [PATCH 3/7] qedi: Set dma_boundary to 0xfff Manish Rangankar
2017-05-19 8:33 ` [PATCH 4/7] qedi: Fix endpoint NULL panic in qedi_set_path Manish Rangankar
2017-05-19 8:33 ` [PATCH 5/7] qedi: Set firmware tcp msl timer value Manish Rangankar
2017-05-19 8:33 ` [PATCH 6/7] qedi: set max_fin_rt default value Manish Rangankar
2017-05-19 8:33 ` [PATCH 7/7] qedi: Fix endpoint NULL panic during recovery Manish Rangankar
2017-05-24 2:17 ` [PATCH 0/7]qedi: Bug fixes Martin K. Petersen
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=20170519083321.18030-1-manish.rangankar@cavium.com \
--to=manish.rangankar@cavium.com \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=cleech@redhat.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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