From: Greg KH <gregkh@linuxfoundation.org>
To: Laura Garcia Liebana <nevola@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 02/10] staging: octeon: Fix alignment with open parenthesis
Date: Fri, 11 Mar 2016 10:13:12 -0800 [thread overview]
Message-ID: <20160311181312.GA10900@kroah.com> (raw)
In-Reply-To: <e0e3978e532e0227d2ffeb8d035bc3cb1bc0b691.1456615452.git.nevola@gmail.com>
On Sun, Feb 28, 2016 at 12:42:07AM +0100, Laura Garcia Liebana wrote:
> Alignment should match open parenthesis. Checkpatch detected these
> issues.
>
> Signed-off-by: Laura Garcia Liebana <nevola@gmail.com>
This patch failed to apply, pleae rebase and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2016-03-11 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 23:41 [PATCH 00/10] staging: octeon: Fix several checkpatch issues Laura Garcia Liebana
2016-02-27 23:41 ` [PATCH 01/10] staging: octeon: Move logical operators on the correct line Laura Garcia Liebana
2016-02-27 23:42 ` [PATCH 02/10] staging: octeon: Fix alignment with open parenthesis Laura Garcia Liebana
2016-03-11 18:13 ` Greg KH [this message]
2016-02-27 23:42 ` [PATCH 03/10] staging: octeon: Insert blank line after struct declaration Laura Garcia Liebana
2016-02-27 23:43 ` [PATCH 04/10] staging: octeon: Remove comparison to NULL Laura Garcia Liebana
2016-02-27 23:43 ` [PATCH 05/10] staging: octeon: Fix block comments Laura Garcia Liebana
2016-02-27 23:44 ` [PATCH 06/10] staging: octeon: Remove blank lines after open brace Laura Garcia Liebana
2016-02-27 23:45 ` [PATCH 07/10] staging: octeon: Fix lines over 80 characters Laura Garcia Liebana
2016-02-27 23:45 ` [PATCH 08/10] staging: octeon: Use type s32 instead of int32_t Laura Garcia Liebana
2016-03-11 18:12 ` [Outreachy kernel] " Greg KH
2016-02-27 23:46 ` [PATCH 09/10] staging: octeon: Remove multiple blank lines Laura Garcia Liebana
2016-02-27 23:47 ` [PATCH 10/10] staging: octeon: Fix braces in condition statement Laura Garcia Liebana
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=20160311181312.GA10900@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=nevola@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.