linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>,
	<gregkh@linuxfoundation.org>
Cc: <outreachy@lists.linux.dev>, <vireshk@kernel.org>,
	<johan@kernel.org>, <elder@kernel.org>,
	<greybus-dev@lists.linaro.org>, <linux-kernel@vger.kernel.org>,
	<linux-staging@lists.linux.dev>, <eng.mennamahmoud.mm@gmail.com>
Subject: Re: [PATCH RESEND] staging: greybus: remove unnecessary blank line
Date: Wed, 22 Mar 2023 11:35:40 -0700	[thread overview]
Message-ID: <641b4a7ca42ab_2ef21c294cc@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20230319132452.151877-2-eng.mennamahmoud.mm@gmail.com>

Menna Mahmoud wrote:
> Remove unnecessary blank line before struct as reported
> by checkpatch:
> 
> " CHECK: Please don't use multiple blank lines "
> 

Reviewed-by: Ira Weiny <ira.weiny@intel.com>

> Signed-off-by: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>
> ---
>  drivers/staging/greybus/greybus_authentication.h | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/staging/greybus/greybus_authentication.h b/drivers/staging/greybus/greybus_authentication.h
> index 7edc7295b7ab..48b4a9794d3c 100644
> --- a/drivers/staging/greybus/greybus_authentication.h
> +++ b/drivers/staging/greybus/greybus_authentication.h
> @@ -41,7 +41,6 @@
>  #define CAP_AUTH_RESULT_CR_NO_KEY	0x03
>  #define CAP_AUTH_RESULT_CR_SIG_FAIL	0x04
>  
> -
>  /* IOCTL support */
>  struct cap_ioc_get_endpoint_uid {
>  	__u8			uid[8];
> -- 
> 2.34.1
> 
> 



      reply	other threads:[~2023-03-22 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 13:24 [PATCH RESEND] staging: greybus: remove unnecessary blank line Menna Mahmoud
2023-03-22 18:35 ` Ira Weiny [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=641b4a7ca42ab_2ef21c294cc@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=elder@kernel.org \
    --cc=eng.mennamahmoud.mm@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    --cc=vireshk@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).