mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Alexon Oliveira <alexondunkan@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	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 alignment should match open parenthesis
Date: Fri, 28 Jul 2023 08:24:56 +0300	[thread overview]
Message-ID: <2354895b-c127-40eb-8f16-b19e4750e1d0@kadam.mountain> (raw)
In-Reply-To: <ZMKrcvpu3b15Hdif@alolivei-thinkpadt480s.gru.csb>

On Thu, Jul 27, 2023 at 02:37:54PM -0300, Alexon Oliveira wrote:
> > 
> > I would have thought you would get a "line is too long" warning, that
> > didn't happen?
> $ pwd
> /home/alolivei/git/kernels/staging
> $ perl scripts/checkpatch.pl --strict -f drivers/staging/vme_user/vme_bridge.h | grep -i parenthesis
> $ 
> Nope. I didn't get any of that. Check it out:

Heh.  The warning is there but you used grep to remove it.

Speaking of long lines.  Could you fix your email client to line wrap at
75 characters.

regards,
dan carpenter


  reply	other threads:[~2023-07-28  5:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08  3:55 Alexon Oliveira
2023-07-27  8:03 ` Greg KH
2023-07-27 14:47   ` Alexon Oliveira
2023-07-27 15:05     ` Greg KH
2023-07-27 17:08       ` Alexon Oliveira
2023-07-27 17:21         ` Greg KH
2023-07-27 17:37           ` Alexon Oliveira
2023-07-28  5:24             ` Dan Carpenter [this message]
2023-07-28 17:43               ` Alexon Oliveira
2023-07-28 17:59                 ` Dan Carpenter
2023-08-01 15:53                   ` Alexon Oliveira
2023-08-04 21:20 Alexon Oliveira
2023-08-05  6:14 ` Greg KH
2023-08-07 15:13   ` Alexon Oliveira
2023-08-07 15:26     ` Greg KH
2023-08-07 20:30       ` 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=2354895b-c127-40eb-8f16-b19e4750e1d0@kadam.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=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®