public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Dietrich <marvin24@gmx.de>
To: Pawel Lebioda <pawel.lebioda89@gmail.com>
Cc: devel@driverdev.osuosl.org,
	Julian Andres Klode <jak@jak-linux.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	ac100@lists.launchpad.net
Subject: Re: [PATCH 0/2] staging: nvec: fix some coding style problems
Date: Sun, 06 Jul 2014 10:26:41 +0200	[thread overview]
Message-ID: <280954076.FMFuBvGU15@fb07-iapwap2> (raw)
In-Reply-To: <cover.1404586529.git.pawel.lebioda89@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 474 bytes --]

Hi Pawel,

Am Samstag, 5. Juli 2014, 22:30:54 schrieb Pawel Lebioda:
> The following patches fix some warnings reported by checkpatch.pl
> 
> Pawel Lebioda (2):
>   staging: nvec: remove unnecessary 'else' after 'return' statement
>   staging: nvec: remove unneccessary 'out of memory' message
> 
>  drivers/staging/nvec/nvec.c | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)

thanks for fixing, so for this series

Acked-by: Marc Dietrich <marvin24@gmx.de>

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 169 bytes --]

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

      parent reply	other threads:[~2014-07-06  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 20:30 [PATCH 0/2] staging: nvec: fix some coding style problems Pawel Lebioda
2014-07-05 20:30 ` [PATCH 1/2] staging: nvec: remove unnecessary 'else' after 'return' statement Pawel Lebioda
2014-07-07  5:53   ` Thierry Reding
2014-07-05 20:30 ` [PATCH 2/2] staging: nvec: remove unneccessary 'out of memory' message Pawel Lebioda
2014-07-07  5:53   ` Thierry Reding
2014-07-06  8:26 ` Marc Dietrich [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=280954076.FMFuBvGU15@fb07-iapwap2 \
    --to=marvin24@gmx.de \
    --cc=ac100@lists.launchpad.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jak@jak-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pawel.lebioda89@gmail.com \
    /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