From: Stefano Brivio <sbrivio@redhat.com>
To: Deepak R Varma <mh12gx2825@gmail.com>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org,
daniel.baluta@gmail.com
Subject: Re: [Outreachy kernel] [PATCH v2 1/4] staging: fbtft: Reformat line over 80 characters
Date: Sun, 15 Mar 2020 22:45:42 +0100 [thread overview]
Message-ID: <20200315224542.638e4c40@elisabeth> (raw)
In-Reply-To: <0fbcf3ff3a2b31a643293c0098d70f54e994a405.1584105606.git.mh12gx2825@gmail.com>
Looks good to me, just a few typos I wouldn't normally care about
(unless a patch is fixing typos), but as you might re-post this:
On Fri, 13 Mar 2020 19:12:13 +0530
Deepak R Varma <mh12gx2825@gmail.com> wrote:
> A long variable name beyond 80 characters gets exended into the next
extended
> line. Reformating the line makes it more readable. Also adding an extra
Reformatting
--
Stefano
next prev parent reply other threads:[~2020-03-15 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 13:41 [PATCH v2 0/4] staging: fbtft: code cleanup patchset - checkpatch Deepak R Varma
2020-03-13 13:42 ` [PATCH v2 1/4] staging: fbtft: Reformat line over 80 characters Deepak R Varma
2020-03-15 21:45 ` Stefano Brivio [this message]
2020-03-13 13:43 ` [PATCH v2 2/4] staging: fbtft: Reformat long macro definitions Deepak R Varma
2020-03-15 21:46 ` [Outreachy kernel] " Stefano Brivio
2020-03-13 13:44 ` [PATCH v2 3/4] staging: fbtft: simplify array index computation Deepak R Varma
2020-03-15 21:46 ` [Outreachy kernel] " Stefano Brivio
2020-03-13 13:44 ` [PATCH v2 4/4] staging: fbtft: Avoid potential precedence issues Deepak R Varma
2020-03-15 21:46 ` [Outreachy kernel] " Stefano Brivio
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=20200315224542.638e4c40@elisabeth \
--to=sbrivio@redhat.com \
--cc=daniel.baluta@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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.