From: Greg KH <gregkh@linuxfoundation.org>
To: sharon <sharon.dvir1@mail.huji.ac.il>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Fix coding style warning.
Date: Sat, 8 Nov 2014 08:52:11 -0800 [thread overview]
Message-ID: <20141108165211.GA17400@kroah.com> (raw)
In-Reply-To: <1415464746.12634.10.camel@mail.huji.ac.il>
On Sat, Nov 08, 2014 at 06:39:06PM +0200, sharon wrote:
> Fix coding style warning.
What coding style warning? Be specific please.
And your subject:, you aren't saying where in the kernel you are fixing
anything, look at other patches for this file in git, what did the
subject look like for them?
> (First submission, sorry in advance for any dumb stuff I'm missing.
> Let me know and I'll fix it.)
These two sentances don't need to be here :)
> Signed-off-by: Sharon Dvir <sharon.dvir1@mail.huji.ac.il>
This doesn't match up with what the From: line above says, so please fix
the from: line.
> diff --git a/drivers/staging/android/binder.c
> b/drivers/staging/android/binder.c
> index c69c40d..655c3bf 100644
> --- a/drivers/staging/android/binder.c
> +++ b/drivers/staging/android/binder.c
> @@ -1267,8 +1267,8 @@ static void
> binder_transaction_buffer_release(struct binder_proc *proc,
> switch (fp->type) {
> case BINDER_TYPE_BINDER:
> case BINDER_TYPE_WEAK_BINDER: {
> - struct binder_node *node = binder_get_node(proc, fp->binder);
> -
> + struct binder_node *node = binder_get_node(proc,
> + fp->binder);
> if (node == NULL) {
> pr_err("transaction release %d bad node %016llx\n",
> debug_id, (u64)fp->binder);
What tree did you make this against? This file isn't in linux-next
anymore, is it?
thanks,
greg k-h
next prev parent reply other threads:[~2014-11-08 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 16:39 PATCH: Fix coding style warning sharon
2014-11-08 16:52 ` Greg KH [this message]
2014-11-08 21:35 ` Dan Carpenter
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=20141108165211.GA17400@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sharon.dvir1@mail.huji.ac.il \
/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