outreachy.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Gilbert Adikankwu <gilbertadikankwu@gmail.com>
To: gregkh@linuxfoundation.org, outreachy@lists.linux.dev
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Gilbert Adikankwu <gilbertadikankwu@gmail.com>
Subject: [PATCH 0/5] staging: vt6655: Rename variables byCWMaxMin, bySlot, bySIFS, byDIFS and byEIFS
Date: Sun, 22 Oct 2023 00:12:26 +0100	[thread overview]
Message-ID: <cover.1697927812.git.gilbertadikankwu@gmail.com> (raw)

Make the variable names adhere to Linux kernel coding style and fix
checkpatch.pl errors.

Gilbert Adikankwu (5):
  staging: vt6655: Rename variable byCWMaxMin
  staging: vt6655: Rename variable bySlot
  staging: vt6655: Rename variable bySIFS
  staging: vt6655: Rename variable byDIFS
  staging: vt6655: Rename variable byEIFS

 drivers/staging/vt6655/card.c   | 72 ++++++++++++++++-----------------
 drivers/staging/vt6655/device.h | 10 ++---
 2 files changed, 41 insertions(+), 41 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-10-21 23:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 23:12 Gilbert Adikankwu [this message]
2023-10-21 23:12 ` [PATCH 1/5] staging: vt6655: Rename variable byCWMaxMin Gilbert Adikankwu
2023-10-21 23:12 ` [PATCH 2/5] staging: vt6655: Rename variable bySlot Gilbert Adikankwu
2023-10-21 23:12 ` [PATCH 3/5] staging: vt6655: Rename variable bySIFS Gilbert Adikankwu
2023-10-21 23:12 ` [PATCH 4/5] staging: vt6655: Rename variable byDIFS Gilbert Adikankwu
2023-10-21 23:12 ` [PATCH 5/5] staging: vt6655: Rename variable byEIFS Gilbert Adikankwu
2023-10-22  7:09 ` [PATCH 0/5] staging: vt6655: Rename variables byCWMaxMin, bySlot, bySIFS, byDIFS and byEIFS Philipp Hortmann

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.1697927812.git.gilbertadikankwu@gmail.com \
    --to=gilbertadikankwu@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).