From: Greg KH <gregkh@linuxfoundation.org>
To: Anchal Jain <anchalj109@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v3 2/2] staging: wilc1000: Fix lines over 80 characters
Date: Tue, 22 Mar 2016 17:15:46 -0400 [thread overview]
Message-ID: <20160322211546.GA10672@kroah.com> (raw)
In-Reply-To: <f480a579aa22d0a0b4d74d843a5b8d33686324fe.1458649426.git.anchalj109@gmail.com>
On Tue, Mar 22, 2016 at 06:03:49PM +0530, Anchal Jain wrote:
> Break lines so that they do not exceed 80
> characters. Problem found using checkpatch.
>
>
> Signed-off-by: Anchal Jain <anchalj109@gmail.com>
> ---
> changes in v3:
> - Make subject clear
> drivers/staging/wilc1000/linux_mon.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
This patch didn't apply at all to my tree :(
next prev parent reply other threads:[~2016-03-22 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 12:28 [PATCH v3 0/2] Fix multiple warnings Anchal Jain
2016-03-22 12:31 ` [PATCH v3 1/2] staging: wilc1000: Remove camel case in variable names Anchal Jain
2016-03-22 12:33 ` [PATCH v3 2/2] staging: wilc1000: Fix lines over 80 characters Anchal Jain
2016-03-22 21:15 ` Greg KH [this message]
[not found] <cover.1457882673.git.anchalj109@gmail.com>
2016-03-13 15:27 ` Anchal Jain
2016-03-13 15:31 ` [Outreachy kernel] " Julia Lawall
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=20160322211546.GA10672@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anchalj109@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.