All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Efstratios Gavas <xtrat@elg.io>
Cc: devel@driverdev.osuosl.org,
	Thibaut SAUTEREAU <thibaut.sautereau@telecom-sudparis.eu>,
	Christopher H Pezley <chris@pezley.net>,
	linux-kernel@vger.kernel.org,
	AbdAllah-MEZITI <abdallah.meziti.pro@gmail.com>,
	Aviya Erenfeld <aviyae42@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Aviv Palivoda <palaviv@gmail.com>
Subject: Re: [PATCHv3] staging: wlan-ng: prism2sta: fixed indent coding style issues.
Date: Sat, 28 Apr 2018 08:01:41 +0200	[thread overview]
Message-ID: <20180428060141.GC18371@kroah.com> (raw)
In-Reply-To: <2ac130bd.AMIAAAY8Aw8AAAAAAAAAAADFWYgAAAASzIYAAAAAAArW7ABa45e6@mailjet.com>

On Fri, Apr 27, 2018 at 09:33:34PM +0000, Efstratios Gavas wrote:
> Fixed format/style issues found with checkpatch. No code changes.
> Corrected alignment of variables after open parenthesis and line breaks.
> Checkpatch now returns clean except for line over 80 char warnings.
> 
> Signed-off-by: Efstratios Gavas <xtrat@elg.io>
> ---
> v2(unlabled): changed title info
> v3: improved changlog description
> ---
>  drivers/staging/wlan-ng/prism2sta.c | 52 +++++++++++++++++--------------------
>  1 file changed, 24 insertions(+), 28 deletions(-)

Why was this sent twice?  Which one should I take?

I'm dropping both, please only send 1 patch next time.

thanks,

greg k-h

  reply	other threads:[~2018-04-28  6:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27  5:45 [PATCH] Staging: wlan-ng: prism2sta: fixed indent coding style issues Efstratios Gavas
2018-04-27  6:58 ` Greg Kroah-Hartman
2018-04-27 21:33   ` [PATCHv3] staging: " Efstratios Gavas
2018-04-27 21:33   ` Efstratios Gavas
2018-04-28  6:01     ` Greg Kroah-Hartman [this message]
2018-04-28 19:51       ` Efstratios Gavas

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=20180428060141.GC18371@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abdallah.meziti.pro@gmail.com \
    --cc=aviyae42@gmail.com \
    --cc=chris@pezley.net \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=palaviv@gmail.com \
    --cc=thibaut.sautereau@telecom-sudparis.eu \
    --cc=xtrat@elg.io \
    /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.