All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Cristian Sicilia <sicilia.cristian@gmail.com>
Cc: Carmeli Tamir <carmeli.tamir@gmail.com>,
	Christopher Diaz Riveros <chrisadr@gentoo.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Arkadiusz Lis <areklis909@gmail.com>,
	Nathan Chancellor <natechancellor@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Parenthesis fix and temp vars
Date: Fri, 30 Nov 2018 12:21:09 +0100	[thread overview]
Message-ID: <20181130112109.GA14718@kroah.com> (raw)
In-Reply-To: <1543274351-25762-1-git-send-email-sicilia.cristian@gmail.com>

On Tue, Nov 27, 2018 at 12:19:07AM +0100, Cristian Sicilia wrote:
> In the first patch there is a fix of some parenthesis that terminate
> on end of line and some parameters that are not aligned with
> previous parenthesis.
> 
> The second patch is a proposal that avoid the long line refactoring
> code and using a temporary parameter that will be passed to the
> function on next line.

Note, please, in the future put "staging:" in your 0/X emails so they
sort properly in my inbox and it doesn't look odd...

thanks,

greg k-h

      parent reply	other threads:[~2018-11-30 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 23:19 [PATCH 0/2] Parenthesis fix and temp vars Cristian Sicilia
2018-11-26 23:19 ` [PATCH 1/2] staging: emxx_udc: Align parameter with parenthesis Cristian Sicilia
2018-11-26 23:19 ` [PATCH 2/2] staging: emxx_udc: Added a temporary variable with address Cristian Sicilia
2018-11-27  1:44   ` Dan Carpenter
2018-11-27 20:57   ` [PATCH 0/2] Parenthesis fix Cristian Sicilia
2018-11-27 20:57     ` [PATCH 1/2] staging: emxx_udc: Align parameter with parenthesis Cristian Sicilia
2018-12-05  8:44       ` Greg Kroah-Hartman
2018-11-27 20:57     ` [PATCH 2/2] staging: emxx_udc: Remove cast and move all in one line Cristian Sicilia
2018-11-30 11:21 ` Greg Kroah-Hartman [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=20181130112109.GA14718@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=areklis909@gmail.com \
    --cc=carmeli.tamir@gmail.com \
    --cc=chrisadr@gentoo.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    --cc=sicilia.cristian@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 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.