[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8AFC7968D54FB448A30D8F38F259C56233F97479@TK5EX14MBXC114.redmond.corp.microsoft.com>
Date: Tue, 15 Feb 2011 19:09:34 +0000
From: Hank Janssen <hjanssen@...rosoft.com>
To: Greg KH <gregkh@...e.de>
CC: KY Srinivasan <kys@...rosoft.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Hashir Abdi <habdi@...rosoft.com>,
Mike Sterling <Mike.Sterling@...rosoft.com>
Subject: RE: [PATCH ]:Staging: hv: Allocate the vmbus irq dynamically
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@...e.de]
> > Sent: Tuesday, February 15, 2011 9:23 AM
> > > Before the end of the week I will submit two patches for this;
> > >
> > > Remove DPRINT and change it to printk
> >
> > No, use dev_dbg() and friends instead of "raw" printk() calls.
> >
>
> Will do, you caught me just as I was starting the conversion :)
While cleaning this up there are a few places in vmbus and channel behavior
where it is not in a device context. Are printk's okay in that context?
The three drivers network/SCSI and Block of course will use dev_XX family.
Hank.
--
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