From: Dan Carpenter <dan.carpenter@oracle.com>
To: Austin Robinson <austin.rbsn@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: android: ashmem: Replaces printk with pr_err and pr_info
Date: Sat, 14 Jul 2012 15:58:40 +0300 [thread overview]
Message-ID: <20120714125840.GI6056@mwanda> (raw)
In-Reply-To: <1342268914-4547-1-git-send-email-austin.rbsn@gmail.com>
On Sat, Jul 14, 2012 at 08:28:34AM -0400, Austin Robinson wrote:
> In several instances in ashmem.c, printk(KERN_INFO... and printk{KERN_ERR... were being
> used. This replaces those with the preferred pr_err and pr_info, which removes
> style-related warnings.
>
Someone already did this. You should be working against linux-next.
regards,
dan carpenter
prev parent reply other threads:[~2012-07-14 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 12:28 [PATCH] Staging: android: ashmem: Replaces printk with pr_err and pr_info Austin Robinson
2012-07-14 12:58 ` Dan Carpenter [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=20120714125840.GI6056@mwanda \
--to=dan.carpenter@oracle.com \
--cc=austin.rbsn@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.