From: Dan Carpenter <dan.carpenter@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: Matteo Semenzato <mattew8898@gmail.com>,
gregkh@linuxfoundation.org, noralf@tronnes.org,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] Staging: fbtft: fix space errors
Date: Mon, 2 Mar 2015 12:37:04 +0300 [thread overview]
Message-ID: <20150302093704.GE5386@mwanda> (raw)
In-Reply-To: <1425135559.25697.2.camel@perches.com>
On Sat, Feb 28, 2015 at 06:59:19AM -0800, Joe Perches wrote:
> If you're really going to change these, please
> remove the unnecessary \ line continuations
> indent the blocks properly and group the blocks
> more intelligibly. Maybe something like;
>
> static const int st7735r_init[] = {
> -1, 0x01,
> -2, 150,
> -1, 0x11,
> -2, 500,
> -1, 0xB1, 0x01, 0x2C, 0x2D,
> -1, 0xB2, 0x01, 0x2C, 0x2D,
> -1, 0xB3, 0x01, 0x2C, 0x2D, 0x01, 0x2C, 0x2D,
> -1, 0xB4, 0x07,
> -1, 0xC0, 0xA2, 0x02, 0x84,
> -1, 0xC1, 0xC5,
> -1, 0xC2, 0x0A, 0x00,
> -1, 0xC3, 0x8A, 0x2A,
> -1, 0xC4, 0x8A, 0xEE,
> -1, 0xC5, 0x0E,
> -1, 0x20,
> -1, 0x36, 0xC0,
> -1, 0x3A, 0x05,
> -1, 0xE0, 0x0f, 0x1a, 0x0f, 0x18, 0x2f, 0x28, 0x20, 0x22, 0x1f, 0x1b,
> 0x23, 0x37, 0x00, 0x07, 0x02, 0x10,
> -1, 0xE1, 0x0f, 0x1b, 0x0f, 0x17, 0x33, 0x2c, 0x29, 0x2e, 0x30, 0x30,
> 0x39, 0x3f, 0x00, 0x07, 0x03, 0x10,
> -1, 0x29,
> -2, 100,
> -1, 0x13,
> -2, 10,
> -3
> };
What's the logic here? Why are we putting the negatives first?
regards,
dan carpenter
next prev parent reply other threads:[~2015-03-02 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 14:44 [PATCH] Staging: fbtft: fix space errors Matteo Semenzato
2015-02-28 14:59 ` Joe Perches
2015-03-02 9:37 ` Dan Carpenter [this message]
2015-03-02 14:20 ` Joe Perches
2015-03-02 19:21 ` Andrey Skvortsov
2015-03-02 19:39 ` Noralf Trønnes
2015-02-28 16:04 ` [PATCH V2] " Matteo Semenzato
-- strict thread matches above, loose matches on Subject: below --
2015-02-23 16:24 [PATCH] " Matteo Semenzato
2015-03-02 1:16 ` Greg KH
2015-02-22 8:50 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=20150302093704.GE5386@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattew8898@gmail.com \
--cc=noralf@tronnes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox