lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 01 Jun 2015 10:39:56 -0500 From: Bjorn Helgaas <bhelgaas@...gle.com> To: Kashyap Desai <kashyap.desai@...gotech.com>, Uday Lingala <uday.lingala@...gotech.com>, Sumit Saxena <sumit.saxena@...gotech.com> Cc: megaraidlinux.pdl@...gotech.com, "James E.J. Bottomley" <JBottomley@...n.com>, Christoph Hellwig <hch@....de>, linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org Subject: [PATCH v2 0/3] megaraid: use dev_printk() when possible 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 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 | 92 ++++----- drivers/scsi/megaraid/megaraid_sas_base.c | 287 +++++++++++++-------------- drivers/scsi/megaraid/megaraid_sas_fusion.c | 92 ++++----- 3 files changed, 231 insertions(+), 240 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists