From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Devendra Naga <develkernel412222@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
"Mikko Virkkilä" <mikko.virkkila@bluegiga.com>,
"Lauri Hintsala" <Lauri.Hintsala@bluegiga.com>,
"Riku Mettälä" <riku.mettala@bluegiga.com>,
"Veli-Pekka Peltola" <veli-pekka.peltola@bluegiga.com>
Subject: Re: [PATCH 0/5] staging/csr: cleanup patches
Date: Mon, 13 Aug 2012 18:58:28 -0700 [thread overview]
Message-ID: <20120814015828.GA26723@kroah.com> (raw)
In-Reply-To: <1344064508-11975-1-git-send-email-develkernel412222@gmail.com>
On Sat, Aug 04, 2012 at 01:00:08PM +0545, Devendra Naga wrote:
> Actually i have a question about the dbg macros, unifi_warning,
> unifi_error, and unifi_trace,
>
> I think these can be implemented using dev_warn, dev_dbg, functions,
> i mean we can remove these unifi_warning and unifi_error and unifi_trace
> and use the dev_warn and dev_dbg.
Yes, we should use those instead.
thanks,
greg k-h
prev parent reply other threads:[~2012-08-14 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 7:15 [PATCH 0/5] staging/csr: cleanup patches Devendra Naga
2012-08-14 1:58 ` Greg Kroah-Hartman [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=20120814015828.GA26723@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Lauri.Hintsala@bluegiga.com \
--cc=devel@driverdev.osuosl.org \
--cc=develkernel412222@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikko.virkkila@bluegiga.com \
--cc=riku.mettala@bluegiga.com \
--cc=veli-pekka.peltola@bluegiga.com \
/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