From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Sherwin Soltani <sherwin@wybc.com>,
swetland@google.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: staging: android: fix binder.c printk macros
Date: Mon, 25 Jun 2012 10:20:00 -0700 [thread overview]
Message-ID: <1340644800.3359.1.camel@joe2Laptop> (raw)
In-Reply-To: <20120625171715.GA29309@kroah.com>
On Mon, 2012-06-25 at 10:17 -0700, Greg KH wrote:
> On Sat, Jun 23, 2012 at 02:09:41AM -0400, Sherwin Soltani wrote:
> > Changed to pr_warn, pr_err, and pr_info macros and reformatted some
> > lines to bring them under the 80 column limit in the binder.c code.
> >
> > Signed-off-by: Sherwin Soltani <sherwin@wybc.com>
> > ---
> > drivers/staging/android/binder.c | 74 ++++++++++++++++++++------------------
> > 1 file changed, 40 insertions(+), 34 deletions(-)
>
> Hi,
>
> This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
> a patch that has triggered this response. He used to manually respond
> to these common problems, but in order to save his sanity (he kept
> writing the same thing over and over, yet to different people), I was
> created. Hopefully you will not take offence and will fix the problem
> in your patch and resubmit it so that it can be accepted into the Linux
> kernel tree.
> You are receiving this message because of the following common error(s)
> as indicated below:
>
> --- Your patch did many different things all at once, making it
> difficult to review.
Your patch-bot needs work.
Converting printks to pr_<level> is trivial
and should be done all at once, not piecemeal.
next prev parent reply other threads:[~2012-06-25 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 6:09 Sherwin Soltani
2012-06-25 17:17 ` Greg KH
2012-06-25 17:20 ` Joe Perches [this message]
2012-06-25 17:24 ` Greg KH
2012-06-25 17:30 ` Joe Perches
2012-06-25 17:45 ` Greg KH
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=1340644800.3359.1.camel@joe2Laptop \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sherwin@wybc.com \
--cc=swetland@google.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
all inboxes | Powered by JetHome®