From: Jamal Shareef <jamal.k.shareef@gmail.com>
To: boqun.feng@microsoft.com, andrea.parri@microsoft.com
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com,
jamal.k.shareef@gmail.com
Subject: [PATCH 0/2] Fix line over 80 characters warnings
Date: Mon, 14 Oct 2019 20:12:11 -0700 [thread overview]
Message-ID: <cover.1571108943.git.jamal.k.shareef@gmail.com> (raw)
This patchset addresses "line over 80 characters" warnings from
checkpatch.
The patches were split mainly for ease of review, however
- Patch 1 fixes mainly function calls exceeding the 80 character limit
- Patch 2 fixes block comments and variables over the limit
Jamal Shareef (2):
staging: sm750fb: Fix lines over 80 characters
staging: sm750fb: Fix comments and assignments over 80 chars
drivers/staging/sm750fb/ddk750_display.c | 4 +-
drivers/staging/sm750fb/ddk750_mode.c | 5 +-
drivers/staging/sm750fb/ddk750_sii164.c | 28 ++++++----
drivers/staging/sm750fb/ddk750_sii164.h | 11 ++--
drivers/staging/sm750fb/sm750.c | 22 +++++---
drivers/staging/sm750fb/sm750_accel.c | 69 ++++++++++++++++++------
drivers/staging/sm750fb/sm750_accel.h | 51 ++++++++++++++----
7 files changed, 139 insertions(+), 51 deletions(-)
--
2.17.1
next reply other threads:[~2019-10-15 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 3:12 Jamal Shareef [this message]
2019-10-15 3:12 ` [PATCH 1/2] staging: sm750fb: Fix lines over 80 characters Jamal Shareef
2019-10-15 3:12 ` [PATCH 2/2] staging: sm750fb: Fix comments and assignments over 80 chars Jamal Shareef
2019-10-15 16:44 ` [Outreachy kernel] " Greg KH
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=cover.1571108943.git.jamal.k.shareef@gmail.com \
--to=jamal.k.shareef@gmail.com \
--cc=andrea.parri@microsoft.com \
--cc=boqun.feng@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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.