From: Alexon Oliveira <alexondunkan@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: martyn@welchs.me.uk, manohar.vanga@gmail.com,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: vme_user: fix check blank lines not necessary
Date: Mon, 14 Aug 2023 17:31:30 -0300 [thread overview]
Message-ID: <ZNqPIvaQJ9HO8p9x@alolivei-thinkpadt480s.gru.csb> (raw)
In-Reply-To: <2023081448-sustainer-prelaw-25a2@gregkh>
On Mon, Aug 14, 2023 at 10:17:10PM +0200, Greg KH wrote:
> On Mon, Aug 14, 2023 at 04:33:11PM -0300, Alexon Oliveira wrote:
> > Fixed all CHECK: Blank lines aren't necessary after an open brace '{'
> > and CHECK: Blank lines aren't necessary before a close brace '}'
> > as reported by checkpatch to adhere to the Linux kernel
> > coding-style guidelines.
> >
> > Signed-off-by: Alexon Oliveira <alexondunkan@gmail.com>
> > ---
> > drivers/staging/vme_user/vme.c | 5 -----
> > 1 file changed, 5 deletions(-)
> >
> > diff --git a/drivers/staging/vme_user/vme.c b/drivers/staging/vme_user/vme.c
> > index 5eb0d780c77f..c7c50406c199 100644
> > --- a/drivers/staging/vme_user/vme.c
> > +++ b/drivers/staging/vme_user/vme.c
> > @@ -308,7 +308,6 @@ struct vme_resource *vme_slave_request(struct vme_dev *vdev, u32 address,
> > if (((slave_image->address_attr & address) == address) &&
> > ((slave_image->cycle_attr & cycle) == cycle) &&
> > (slave_image->locked == 0)) {
> > -
> > slave_image->locked = 1;
> > mutex_unlock(&slave_image->mtx);
> > allocated_image = slave_image;
> > @@ -510,7 +509,6 @@ struct vme_resource *vme_master_request(struct vme_dev *vdev, u32 address,
> > ((master_image->cycle_attr & cycle) == cycle) &&
> > ((master_image->width_attr & dwidth) == dwidth) &&
> > (master_image->locked == 0)) {
> > -
> > master_image->locked = 1;
> > spin_unlock(&master_image->lock);
> > allocated_image = master_image;
> > @@ -682,10 +680,8 @@ ssize_t vme_master_read(struct vme_resource *resource, void *buf, size_t count,
> > count = length - offset;
> >
> > return bridge->master_read(image, buf, count, offset);
> > -
> > }
> > EXPORT_SYMBOL(vme_master_read);
> > -
>
> This line needs to be there, checkpatch should not have complained about
> it.
>
Hmm, ACK. It complained, as below:
CHECK: Blank lines aren't necessary after an open brace '{'
#311: FILE: drivers/staging/vme_user/vme.c:311:
+ (slave_image->locked == 0)) {
+
--
CHECK: Blank lines aren't necessary after an open brace '{'
#513: FILE: drivers/staging/vme_user/vme.c:513:
+ (master_image->locked == 0)) {
+
--
CHECK: Blank lines aren't necessary before a close brace '}'
#684: FILE: drivers/staging/vme_user/vme.c:684:
+
+}
--
CHECK: Blank lines aren't necessary before a close brace '}'
#686: FILE: drivers/staging/vme_user/vme.c:686:
+
+}
--
CHECK: Blank lines aren't necessary after an open brace '{'
#890: FILE: drivers/staging/vme_user/vme.c:890:
+ (dma_ctrlr->locked == 0)) {
+
--
Should I keep them then and forget this patch?
> thanks,
>
> greg k-h
Thank you.
Alexon Oliveira
next prev parent reply other threads:[~2023-08-14 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 19:33 Alexon Oliveira
2023-08-14 20:17 ` Greg KH
2023-08-14 20:31 ` Alexon Oliveira [this message]
2023-08-14 20:46 ` Greg KH
2023-08-14 20:51 ` Alexon Oliveira
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=ZNqPIvaQJ9HO8p9x@alolivei-thinkpadt480s.gru.csb \
--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 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®