The current megaraid driver messages are somewhat inconsistent, with
different combinations of driver name and device address:
megasas: 0x1000:0x005b:0x15d9:0x0690: bus 1:slot 0:func 0
megaraid_sas 0000:01:00.0: megasas: FW restarted successfully from
megasas_init_fw!
megasas: Waiting for FW to come to ready state
These patches use dev_printk() to include the driver name and device
address in the conventional format.
Changes between v2 and v3:
- Rebase to v4.2-rc1
- Fix more whitespace issues (but not all) in megaraid_sas_base.c
Changes between v1 and v2:
- Rebase to next-20150601
- Squash megaraid_sas_base.c and megaraid_sas_fusion.c changes into one patch
- Split megasas_dump_pending_frames() run-on printks into one line each
- Add patch to fix whitespace errors in megasas_dump_pending_frames()
---
Bjorn Helgaas (3):
megaraid : use dev_printk when possible
megaraid_sas : use dev_printk when possible
megaraid_sas : fix whitespace errors
drivers/scsi/megaraid.c | 140 +++----
drivers/scsi/megaraid/megaraid_sas_base.c | 544 +++++++++++++--------------
drivers/scsi/megaraid/megaraid_sas_fusion.c | 95 ++---
3 files changed, 378 insertions(+), 401 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
