From: Richard Purdie <rpurdie@rpsys.net>
To: David Brownell <david-b@pacbell.net>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Samsung LTV350QV LCD driver
Date: Tue, 29 May 2007 23:19:43 +0100 [thread overview]
Message-ID: <1180477183.5822.105.camel@localhost.localdomain> (raw)
In-Reply-To: <200705291438.11581.david-b@pacbell.net>
On Tue, 2007-05-29 at 14:38 -0700, David Brownell wrote:
> On Tuesday 29 May 2007, Richard Purdie wrote:
> > The LCD class device bits look fine to me. The only change I'd request
> > is not to change the order of things in drivers/video/backlight/Kconfig.
> > If you do want to reword one of those entries (which is what I think you
> > wanted to do), send it as a separate patch please.
>
> One significant issue was screwed up sequencing causing
> tools like 'xconfig' to display things wrong. Appended
> is a patch fixing just that goof.
Put it like that, applied, thanks. :)
(http://git.o-hand.com/?p=linux-rpurdie-backlight;a=shortlog;h=for-mm)
> > David, any objections to the SPI bits?
>
> They seemed fine to me, other than the write_reg() macro
> having an embedded 'goto' ... explicitly against the
> Documentation/CodingStyle guidelines. ("Chapter 12",
> point 1 = "macros that affect code flow".)
Yes, even if it will make the code more ugly in a way, I think it needs
to be changed...
> I like seeing more of the SPI drivers go upstream. ;)
;)
Cheers,
Richard
next prev parent reply other threads:[~2007-05-29 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 19:52 Haavard Skinnemoen
2007-05-29 21:01 ` Richard Purdie
2007-05-29 21:38 ` David Brownell
2007-05-29 22:19 ` Richard Purdie [this message]
2007-05-30 10:46 ` [PATCH v2] " Haavard Skinnemoen
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=1180477183.5822.105.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=david-b@pacbell.net \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome