From: Brian King <brking@linux.vnet.ibm.com>
To: "Patro, Sumant" <Sumant.Patro@lsi.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-scsi@vger.kernel.org, "Kolli, Neela" <Neela.Kolli@lsi.com>,
"Yang, Bo" <Bo.Yang@lsi.com>
Subject: Re: [PATCH] [MEGARAID_SAS]: Use pr_info
Date: Fri, 10 Aug 2007 13:26:33 -0500 [thread overview]
Message-ID: <46BCADD9.4090304@linux.vnet.ibm.com> (raw)
In-Reply-To: <0631C836DBF79F42B5A60C8C8D4E8229BF1885@NAMAIL2.ad.lsil.com>
Patro, Sumant wrote:
> Hello Arnaldo,
>
> Throughout the megaraid_sas driver code there are printk's with
> appropriate flags (that includes KERN_INFO). What is the incentive to
> change printk with KERN_INFO to pr_info?
And why not change most of these to dev_printk and friends?
-Brian
>
> Regards,
>
> Sumant
>
> -----Original Message-----
> From: Arnaldo Carvalho de Melo [mailto:arnaldo.melo@gmail.com] On Behalf
> Of Arnaldo Carvalho de Melo
> Sent: Wednesday, August 08, 2007 4:15 PM
> To: DL-MegaRAID Linux
> Cc: linux-scsi@vger.kernel.org; James Bottomley
> Subject: [PATCH] [MEGARAID_SAS]: Use pr_info
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> ---
> drivers/scsi/megaraid/megaraid_sas.c | 14 ++++++--------
> 1 files changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/scsi/megaraid/megaraid_sas.c
> b/drivers/scsi/megaraid/megaraid_sas.c
> index 59099da..4a8cf06 100644
> --- a/drivers/scsi/megaraid/megaraid_sas.c
> +++ b/drivers/scsi/megaraid/megaraid_sas.c
> @@ -1341,8 +1341,7 @@ megasas_transition_to_ready(struct
> megasas_instance* instance)
> fw_state =
> instance->instancet->read_fw_status_reg(instance->reg_set) &
> MFI_STATE_MASK;
>
> if (fw_state != MFI_STATE_READY)
> - printk(KERN_INFO "megasas: Waiting for FW to come to
> ready"
> - " state\n");
> + pr_info("megasas: Waiting for FW to come to ready
> state\n");
>
> while (fw_state != MFI_STATE_READY) {
>
> @@ -1444,7 +1443,7 @@ megasas_transition_to_ready(struct
> megasas_instance* instance)
> return -ENODEV;
> }
> };
> - printk(KERN_INFO "megasas: FW now in Ready state\n");
> + pr_info("megasas: FW now in Ready state\n");
>
> return 0;
> }
> @@ -2277,9 +2276,9 @@ megasas_probe_one(struct pci_dev *pdev, const
> struct pci_device_id *id)
> /*
> * Announce PCI information
> */
> - printk(KERN_INFO "megasas: %#4.04x:%#4.04x:%#4.04x:%#4.04x: ",
> - pdev->vendor, pdev->device, pdev->subsystem_vendor,
> - pdev->subsystem_device);
> + pr_info("megasas: %#4.04x:%#4.04x:%#4.04x:%#4.04x: ",
> + pdev->vendor, pdev->device, pdev->subsystem_vendor,
> + pdev->subsystem_device);
>
> printk("bus %d:slot %d:func %d\n",
> pdev->bus->number, PCI_SLOT(pdev->devfn),
> PCI_FUNC(pdev->devfn)); @@ -3030,8 +3029,7 @@ static int __init
> megasas_init(void)
> /*
> * Announce driver version and other information
> */
> - printk(KERN_INFO "megasas: %s %s\n", MEGASAS_VERSION,
> - MEGASAS_EXT_VERSION);
> + pr_info("megasas: %s %s\n", MEGASAS_VERSION,
> MEGASAS_EXT_VERSION);
>
> /*
> * Register character device node
> --
> 1.5.2.2
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
prev parent reply other threads:[~2007-08-10 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 23:14 [PATCH] [MEGARAID_SAS]: Use pr_info Arnaldo Carvalho de Melo
2007-08-10 18:18 ` Patro, Sumant
2007-08-10 18:26 ` Brian King [this message]
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=46BCADD9.4090304@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=Bo.Yang@lsi.com \
--cc=Neela.Kolli@lsi.com \
--cc=Sumant.Patro@lsi.com \
--cc=acme@ghostprotocols.net \
--cc=linux-scsi@vger.kernel.org \
/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