From: Benjamin Philip <benjamin.philip495@gmail.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Benjamin Philip <benjamin.philip495@gmail.com>
Subject: [PATCH 0/4] staging: sm750fb: Remove CamelCase in lynxfb_crtc
Date: Wed, 28 Jul 2021 00:49:49 +0530 [thread overview]
Message-ID: <cover.1627413010.git.benjamin.philip495@gmail.com> (raw)
This patchset (as the subject implies) renames some struct members to follow
the snake_case naming convention from CamelCase. By doing so, it also fixes
2 checkpatch CHECKs.
To test it, I have checked if the module builds, which it does. I have also
ensured that checkpatch.pl does not issue any new warnings.
Also, is this patchset fine or should I have clubbed it into one big commit,
Greg?
Thanks,
Benjamin Philip
Benjamin Philip (4):
staging: sm750fb: Rename oScreen to o_screen in lynxfb_crtc
staging: sm750fb: Rename oCursor to o_cursor in lynxfb_crtc
staging: sm750fb: Rename vCursor to v_cursor in lynxfb_crtc
staging: sm750fb: Rename vScreen to v_screen in lynxfb_crtc
drivers/staging/sm750fb/sm750.c | 44 ++++++++++-----------
drivers/staging/sm750fb/sm750.h | 8 ++--
drivers/staging/sm750fb/sm750_hw.c | 62 +++++++++++++++---------------
3 files changed, 57 insertions(+), 57 deletions(-)
--
2.31.1
next reply other threads:[~2021-07-27 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 19:19 Benjamin Philip [this message]
2021-07-27 19:19 ` [PATCH 1/4] staging: sm750fb: Rename oScreen to o_screen in lynxfb_crtc Benjamin Philip
2021-07-27 19:19 ` [PATCH 2/4] staging: sm750fb: Rename oCursor to o_cursor " Benjamin Philip
2021-07-27 19:19 ` [PATCH 3/4] staging: sm750fb: Rename vCursor to v_cursor " Benjamin Philip
2021-07-27 19:19 ` [PATCH 4/4] staging: sm750fb: Rename vScreen to v_screen " Benjamin Philip
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.1627413010.git.benjamin.philip495@gmail.com \
--to=benjamin.philip495@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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.