From: Dan Carpenter <dan.carpenter@oracle.com>
To: Matteo Semenzato <mattew8898@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] Staging: fbtft: fix coding style errors
Date: Mon, 2 Mar 2015 16:23:14 +0300 [thread overview]
Message-ID: <20150302132314.GB5437@mwanda> (raw)
In-Reply-To: <1425302132.3928.17.camel@gmail.com>
On Mon, Mar 02, 2015 at 02:15:32PM +0100, Matteo Semenzato wrote:
> >
> > For some reason you put the line breaks at the negative numbers? Why?
> >
> > regards,
> > dan carpenter
> >
> -1, -2 and -3 are the init sequence markers: -1: command begin, -2:
> millisecond delay, -3: end of init sequence
Cool. Put that in the changelog.
regards,
dan carpenter
next prev parent reply other threads:[~2015-03-02 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 14:31 [PATCH] Staging: fbtft: fix coding style errors Matteo Semenzato
2015-02-28 17:37 ` [PATCH V2] " Matteo Semenzato
2015-03-02 1:17 ` Greg KH
2015-03-02 9:29 ` Dan Carpenter
2015-03-02 13:15 ` Matteo Semenzato
2015-03-02 13:23 ` Dan Carpenter [this message]
2015-03-02 13:35 ` Matteo Semenzato
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=20150302132314.GB5437@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattew8898@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