All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexon Oliveira <alexondunkan@gmail.com>
To: gregkh@linuxfoundation.org
Cc: martyn@welchs.me.uk, manohar.vanga@gmail.com,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
	Alexon Oliveira <alexondunkan@gmail.com>
Subject: [PATCH 0/4] staging: vme_user: fix checks reported in vme_fake.c
Date: Sat, 26 Aug 2023 18:05:14 -0300	[thread overview]
Message-ID: <cover.1693082101.git.alexondunkan@gmail.com> (raw)

The goal of this series is to fix all warnings related to
aligment of open parenthesis, lines not ending with '(',
unnecessary blank lines and unnecessary space after a cast
in the vme_fake.c file, as reported by checkpatch to adhere
to the Linux kernel coding-style guidelines.

Alexon Oliveira (4):
  staging: vme_user: fix check alignment of open parenthesis in
    vme_fake.c
  staging: vme_user: fix check lines not ending with '(' in vme_fake.c
  staging: vme_user: fix check unnecessary blank lines in vme_fake.c
  staging: vme_user: fix check unnecessary space after a cast in
    vme_fake.c

 drivers/staging/vme_user/vme_fake.c | 72 ++++++++++++++---------------
 1 file changed, 35 insertions(+), 37 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-08-26 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26 21:05 Alexon Oliveira [this message]
2023-08-26 21:05 ` [PATCH 1/4] staging: vme_user: fix check alignment of open parenthesis in vme_fake.c Alexon Oliveira
2023-08-26 21:05 ` [PATCH 2/4] staging: vme_user: fix check lines not ending with '(' " Alexon Oliveira
2023-08-26 21:05 ` [PATCH 3/4] staging: vme_user: fix check unnecessary blank lines " Alexon Oliveira
2023-08-26 21:05 ` [PATCH 4/4] staging: vme_user: fix check unnecessary space after a cast " Alexon Oliveira
2023-08-27 18:59 ` [PATCH 0/4] staging: vme_user: fix checks reported " Greg KH

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.1693082101.git.alexondunkan@gmail.com \
    --to=alexondunkan@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=manohar.vanga@gmail.com \
    --cc=martyn@welchs.me.uk \
    /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.