From: Ching Huang <ching2048@areca.com.tw>
To: martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
jthumshirn@suse.de, hare@suse.de, dan.carpenter@oracle.com,
hch@infradead.org
Subject: [PATCH 0/13] scsi: arcmsr: add some driver options and support new adapter ARC-1884
Date: Thu, 09 Nov 2017 07:16:21 +0800 [thread overview]
Message-ID: <1510182981.4523.48.camel@Centos6.3-64> (raw)
From: Ching Huang <ching2048@areca.com.tw>
Hi all,
The following patches apply to Martin's 4.15/scsi-queue.
Patch 1: redefine ACB_ADAPTER_TYPE_A, _B, _C, _D and subsequent changes.
Patch 2: simplify arcmsr_iop_init function.
Patch 3: add codes for ACB_ADAPTER_TYPE_E to support new adapter ARC-1884
Patch 4: replace constant ARCMSR_MAX_FREECCB_NUM by variable acb->maxFreeCCB that was got from firmware.
Patch 5: add driver option host_can_queue to set host->can_queue value by user. It's value expands
up to 1024.
Patch 6: replace constant ARCMSR_MAX_OUTSTANDING_CMD by variable acb->maxOutstanding that was determined by user.
Patch 7: add driver option cmd_per_lun to set host->cmd_per_lun value by user.
Patch 8: add ACB_F_MSG_GET_CONFIG to acb->acb_flags for for message interrupt checking before schedule work for
get device map.
Patch 9: add a function arcmsr_set_iop_datetime and driver option set_date_time to set date and time to firmware.
Patch 10: fix clear doorbell queue on ACB_ADAPTER_TYPE_B controller.
Patch 11: spin off duplicate code of timer init for message isr BH in arcmsr_probe and arcmsr_resume as a function
arcmsr_init_get_devmap_timer
Patch 12: adjust some tab or white-space to make text alignment.
Patch 13: update driver version to v1.40.00.02-20171011
Please review. Thanks.
---
next reply other threads:[~2017-11-09 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 23:16 Ching Huang [this message]
2017-11-08 23:37 Ching Huang
2017-11-21 3:03 ` Martin K. Petersen
2017-11-20 19:48 ` Ching Huang
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=1510182981.4523.48.camel@Centos6.3-64 \
--to=ching2048@areca.com.tw \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dan.carpenter@oracle.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®