All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mike <lameli67@gmail.com>
Cc: samuel@sortiz.org, meghana.madhyastha@gmail.com,
	julia.lawall@lip6.fr, davem@davemloft.net, dhowells@redhat.com,
	netdev@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, lameli67@yandex.ru
Subject: Re: [PATCH 00/10] Code style patches for staging/irda
Date: Sat, 2 Dec 2017 08:31:42 +0000	[thread overview]
Message-ID: <20171202083142.GA13068@kroah.com> (raw)
In-Reply-To: <cover.1511645554.git.lameli67@gmail.com>

On Sun, Nov 26, 2017 at 01:45:55AM +0300, Mike wrote:
> 
> This is my task from Little Penguin :)

What does that mean?

> 
> Mike (10):
>   trailing whitespace fixed
>   spaces before tabs are fixed
>   trailing */ on a separate line fixed
>   if-else code style fixed
>   space prohibited before that ',' fixed
>   space required before the open parenthesis - fixed
>   code indent should use tabs where possible - fixed
>   spaces required - fixed
>   others not regular and missed errors are fixed
>   lines over 80 characters are fixed
> 
>  drivers/staging/irda/drivers/ali-ircc.c | 1516 +++++++++++++++----------------
>  1 file changed, 722 insertions(+), 794 deletions(-)

Did you read drivers/staging/irda/TODO ?

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Mike <lameli67@gmail.com>
Cc: devel@driverdev.osuosl.org, samuel@sortiz.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	lameli67@yandex.ru, dhowells@redhat.com, julia.lawall@lip6.fr,
	meghana.madhyastha@gmail.com, davem@davemloft.net
Subject: Re: [PATCH 00/10] Code style patches for staging/irda
Date: Sat, 2 Dec 2017 08:31:42 +0000	[thread overview]
Message-ID: <20171202083142.GA13068@kroah.com> (raw)
In-Reply-To: <cover.1511645554.git.lameli67@gmail.com>

On Sun, Nov 26, 2017 at 01:45:55AM +0300, Mike wrote:
> 
> This is my task from Little Penguin :)

What does that mean?

> 
> Mike (10):
>   trailing whitespace fixed
>   spaces before tabs are fixed
>   trailing */ on a separate line fixed
>   if-else code style fixed
>   space prohibited before that ',' fixed
>   space required before the open parenthesis - fixed
>   code indent should use tabs where possible - fixed
>   spaces required - fixed
>   others not regular and missed errors are fixed
>   lines over 80 characters are fixed
> 
>  drivers/staging/irda/drivers/ali-ircc.c | 1516 +++++++++++++++----------------
>  1 file changed, 722 insertions(+), 794 deletions(-)

Did you read drivers/staging/irda/TODO ?

       reply	other threads:[~2017-12-02  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1511645554.git.lameli67@gmail.com>
2017-12-02  8:31 ` Greg KH [this message]
2017-12-02  8:31   ` [PATCH 00/10] Code style patches for staging/irda Greg KH
     [not found] ` <3dc8635bc62c888f69af2ed6eb8c004c3df00b05.1511645554.git.lameli67@gmail.com>
2017-12-02  8:32   ` [PATCH 01/10] trailing whitespace fixed 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=20171202083142.GA13068@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=dhowells@redhat.com \
    --cc=julia.lawall@lip6.fr \
    --cc=lameli67@gmail.com \
    --cc=lameli67@yandex.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meghana.madhyastha@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=samuel@sortiz.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 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.