From: Greg KH <gregkh@linuxfoundation.org>
To: Deepak R Varma <mh12gx2825@gmail.com>
Cc: outreachy-kernel@googlegroups.com, daniel.baluta@gmail.com
Subject: Re: [PATCH] staging: fbtft: Reformat lines over 80 characters
Date: Thu, 12 Mar 2020 09:19:36 +0100 [thread overview]
Message-ID: <20200312081936.GG11746@kroah.com> (raw)
In-Reply-To: <20200311212939.GA2872@deeUbuntu>
On Thu, Mar 12, 2020 at 02:59:43AM +0530, Deepak R Varma wrote:
> Multiple macro definitions crossings 80 character line length nakes it
> hard to understand. Reformating the these lines makes the code more
> readable and easy to understand. Issue flagged by checkpatch script.
>
> Signed-off-by: Deepak R Varma <mh12gx2825@gmail.com>
> ---
> drivers/staging/fbtft/fbtft.h | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
You sent 2 patches with almost identical subject lines, yet they did
different things to different files.
Please fix up and make them more unique and resend both of them.
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-12 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 21:29 [PATCH] staging: fbtft: Reformat lines over 80 characters Deepak R Varma
2020-03-12 8:19 ` Greg KH [this message]
2020-03-12 14:23 ` DEEPAK VARMA
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=20200312081936.GG11746@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.baluta@gmail.com \
--cc=mh12gx2825@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.