All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jerom van der Sar <jerom.vandersar@gmail.com>
Cc: philipp.g.hortmann@gmail.com, error27@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: rtl8192e: space formatting fixes in rtl_cam.c
Date: Tue, 8 Nov 2022 16:21:10 +0100	[thread overview]
Message-ID: <Y2pz5twhWN2eJT24@kroah.com> (raw)
In-Reply-To: <20221102200057.397-1-jerom.vandersar@gmail.com>

On Wed, Nov 02, 2022 at 09:00:58PM +0100, Jerom van der Sar wrote:
> Fixed a few coding style issues in rtl_cam.c: two times lack of
> spaces around binary operators. Some other warnings still remain.
> These issues were found by scripts/checkpatch.pl.
> 
> This patch helps clean up the rtl8192e driver in staging, making it
> easier to read and maintain.
> 
> Signed-off-by: Jerom van der Sar <jerom.vandersar@gmail.com>
> ---
> Changes in v4:
>  - Reverted more double blank line formatting fixes to make the patch
>    even smaller.

Does not apply to my tree :(

      parent reply	other threads:[~2022-11-08 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 22:51 [PATCH] staging: rtl8192e: cleanup coding style issues with spacing Jerom van der Sar
2022-10-31 23:07 ` Philipp Hortmann
2022-11-01 21:52   ` [PATCH v2] staging: rtl8192e: space formatting fixes in rtl_cam.c Jerom van der Sar
2022-11-01 22:07     ` Philipp Hortmann
2022-11-01 22:25       ` Jerom van der Sar
2022-11-01 22:29       ` [PATCH v3] " Jerom van der Sar
2022-11-02  7:24         ` Greg KH
2022-11-02 20:00           ` [PATCH v4] " Jerom van der Sar
2022-11-02 22:00             ` Philipp Hortmann
2022-11-08 15:21             ` Greg KH [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=Y2pz5twhWN2eJT24@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=error27@gmail.com \
    --cc=jerom.vandersar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=philipp.g.hortmann@gmail.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.