linux-kernel - [PATCH 0/3] megaraid: use dev

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 28 Apr 2015 18:13:57 -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>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: [PATCH 0/3] megaraid: use dev_printk() when possible

The current megaraid driver messages are somewhat inconsistent, e.g.,

  megasas: 06.803.01.00-rc1 Mon. Mar. 10 17:00:00 PDT 2014
  megasas: 0x1000:0x005b:0x15d9:0x0690: bus 1:slot 0:func 0
  megasas: FW now in Ready state
  megaraid_sas 0000:01:00.0: enabling device (0000 -> 0002)
  megasas: Waiting for FW to come to ready state
  megasas: FW in FAULT state!!
  megaraid_sas 0000:01:00.0: megasas: FW restarted successfully from megasas_init_fw!
  megasas: Waiting for FW to come to ready state
  megasas: FW in FAULT state!!

These patches use dev_printk() to include the driver name and device
address in the conventional format.

---

Bjorn Helgaas (3):
      megaraid: use dev_printk when possible
      megaraid_sas: use dev_printk when possible
      megaraid_sas: use dev_printk when possible

 drivers/scsi/megaraid.c                     |   92 ++++-----
 drivers/scsi/megaraid/megaraid_sas_base.c   |  281 +++++++++++++--------------
 drivers/scsi/megaraid/megaraid_sas_fusion.c |   96 +++++----
 3 files changed, 230 insertions(+), 239 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/