mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Solomon Tan <wjsota@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	dan.carpenter@oracle.com
Subject: [PATCH 0/7] staging: rtl8192e: Remove unnecessary u8 and u16 casts
Date: Sat, 23 Apr 2022 21:01:43 +0800	[thread overview]
Message-ID: <20220423130150.161903-1-wjsota@gmail.com> (raw)

Hi,

This series of patches removes unnecessary explicit u8 and u16 type
casts. They are broken down into 7 patches as follows:

Patch 1 removes u8 casts in assignment statements of u8 variables.
Patch 2 removes u8 casts in u8 arguments to function calls.
Patch 3 removes u8 casts in comparison expressions.
Patch 4 removes u16 casts in assignment statements.
Patch 5 removes the u16 cast in the u16 argument to a function call.
Patch 6 removes the u16 cast because the function parameter is u32.
Patch 7 removes the u16 cast from a function return statement.

Justification is found in the respective changelogs.

Cheers,
Solomon



             reply	other threads:[~2022-04-23 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 13:01 Solomon Tan [this message]
2022-04-23 13:01 ` [PATCH 1/7] staging: rtl8192e: Remove unnecessary u8 assignment cast Solomon Tan
2022-04-23 13:01 ` [PATCH 2/7] staging: rtl8192e: Remove unnecessary u8 argument cast Solomon Tan
2022-04-23 13:01 ` [PATCH 3/7] staging: rtl8192e: Remove unnecessary u8 cast in comparison Solomon Tan
2022-04-23 13:01 ` [PATCH 4/7] staging: rtl8192e: Remove unnecessary u16 assignment cast Solomon Tan
2022-04-23 13:01 ` [PATCH 5/7] staging: rtl8192e: Remove unnecessary u16 argument cast Solomon Tan
2022-04-23 13:01 ` [PATCH 6/7] staging: rtl8192e: Remove u16 cast for u32 parameter Solomon Tan
2022-04-23 13:01 ` [PATCH 7/7] staging: rtl8192e: Remove u16 cast for u16 return value Solomon Tan

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=20220423130150.161903-1-wjsota@gmail.com \
    --to=wjsota@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@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

all inboxes | Powered by JetHome®