[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A961433CDFF2F640A2866803152E61F9516EEACD@G4W3218.americas.hpqcorp.net>
Date: Tue, 4 Dec 2012 20:14:10 +0000
From: "Ortiz, Lance E" <lance.oritz@...com>
To: Mauro Carvalho Chehab <mchehab@...hat.com>
CC: "bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"lance_ortiz@...mail.com" <lance_ortiz@...mail.com>,
"jiang.liu@...wei.com" <jiang.liu@...wei.com>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"bp@...en8.de" <bp@...en8.de>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v6 2/3] aerdrv: Enhanced AER logging
> > + if (!dev) {
> > + pr_info("PCI AER Cannot get PCI device
> %04x:%02x:%02x.%d\n",
> > + pcie->device_id.segment, pcie->device_id.bus,
> > + pcie->device_id.slot, pcie->device_id.function);
>
> Hmm... please correct if I'm wrong, but an error happened at PCI, and
> also a
> kernel bug that prevented it to get the proper PCI device...
>
> IMHO, the message here should be stronger, and likely printed via
> pr_err().
>
Mauro,
I modeled this message after other places in the kernel where this function failed. So I figured it would be safe to be consistent there. I agree though that it should be pr_err(). I can make that change.
--
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