mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Aaron Lawrence <t4rmin@zohomail.com>, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192e: rtllib_crypt_wep: multiple blank lines removal
Date: Tue, 25 Oct 2022 20:03:07 +0200	[thread overview]
Message-ID: <262e9819-88c4-abc9-dcce-ee020b847c6a@gmail.com> (raw)
In-Reply-To: <20221025104402.xvbfobi7sdnwlqs2@plymouth>

On 10/25/22 12:44, Aaron Lawrence wrote:
> Removal of multiple unnecessary blank lines in accordance with the
> Linux kernel coding-style regulations. Said issues ware detected on
> this file by the checkpatch script.
> 
> Signed-off-by: Aaron Lawrence <t4rmin@zohomail.com>
> ---
>   drivers/staging/rtl8192e/rtllib_crypt_wep.c | 8 --------
>   1 file changed, 8 deletions(-)
> 
> diff --git a/drivers/staging/rtl8192e/rtllib_crypt_wep.c b/drivers/staging/rtl8192e/rtllib_crypt_wep.c
> index 7790271a6a40..062285e4d939 100644
> --- a/drivers/staging/rtl8192e/rtllib_crypt_wep.c
> +++ b/drivers/staging/rtl8192e/rtllib_crypt_wep.c
> @@ -27,7 +27,6 @@ struct prism2_wep_data {
>   	struct arc4_ctx tx_ctx_arc4;
>   };
>   
> -
>   static void *prism2_wep_init(int keyidx)
>   {
>   	struct prism2_wep_data *priv;
> @@ -46,7 +45,6 @@ static void *prism2_wep_init(int keyidx)
>   	return priv;
>   }
>   
> -
>   static void prism2_wep_deinit(void *priv)
>   {
>   	kfree_sensitive(priv);
> @@ -120,7 +118,6 @@ static int prism2_wep_encrypt(struct sk_buff *skb, int hdr_len, void *priv)
>   	return 0;
>   }
>   
> -
>   /* Perform WEP decryption on given struct buffer. Buffer includes whole WEP
>    * part of the frame: IV (4 bytes), encrypted payload (including SNAP header),
>    * ICV (4 bytes). len includes both IV and ICV.
> @@ -180,7 +177,6 @@ static int prism2_wep_decrypt(struct sk_buff *skb, int hdr_len, void *priv)
>   	return 0;
>   }
>   
> -
>   static int prism2_wep_set_key(void *key, int len, u8 *seq, void *priv)
>   {
>   	struct prism2_wep_data *wep = priv;
> @@ -194,7 +190,6 @@ static int prism2_wep_set_key(void *key, int len, u8 *seq, void *priv)
>   	return 0;
>   }
>   
> -
>   static int prism2_wep_get_key(void *key, int len, u8 *seq, void *priv)
>   {
>   	struct prism2_wep_data *wep = priv;
> @@ -207,7 +202,6 @@ static int prism2_wep_get_key(void *key, int len, u8 *seq, void *priv)
>   	return wep->key_len;
>   }
>   
> -
>   static void prism2_wep_print_stats(struct seq_file *m, void *priv)
>   {
>   	struct prism2_wep_data *wep = priv;
> @@ -231,13 +225,11 @@ static struct lib80211_crypto_ops rtllib_crypt_wep = {
>   	.owner			= THIS_MODULE,
>   };
>   
> -
>   static int __init rtllib_crypto_wep_init(void)
>   {
>   	return lib80211_register_crypto_ops(&rtllib_crypt_wep);
>   }
>   
> -
>   static void __exit rtllib_crypto_wep_exit(void)
>   {
>   	lib80211_unregister_crypto_ops(&rtllib_crypt_wep);

Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>

      reply	other threads:[~2022-10-25 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 10:44 Aaron Lawrence
2022-10-25 18:03 ` Philipp Hortmann [this message]

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=262e9819-88c4-abc9-dcce-ee020b847c6a@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=t4rmin@zohomail.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 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®