From: Jonathan Larmour <jifl@eCosCentric.com>
To: Sergei Gavrikov <sg@belvok.com>
Cc: eCos patches list <ecos-patches@ecos.sourceware.org>
Subject: Re: SPI lpc2xxx patch
Date: Tue, 17 Feb 2009 09:09:00 -0000 [thread overview]
Message-ID: <499A7EE3.9000502@eCosCentric.com> (raw)
In-Reply-To: <20090217074111.GA15824@sg-ubuntu.local>
Sergei Gavrikov wrote:
> On Tue, Feb 17, 2009 at 12:54:40AM +0000, Jonathan Larmour wrote:
>
>>Sergei Gavrikov wrote:
>>
>>>Hi
>>>
>>>I never try SPI driver for lpc2xxx before, today I did and found an
>>>annoyance copy & paste typo in spi_lpc2xxx_set_config(). Also, to be
>>>ensure the SPI interrupts are using different, was entered a priority
>>>selector, like that was done for the lpc2xxx serial driver.
>>
>>Thanks for the patch. I've checked it in with some minor mods, primarily
>>placing the new options under the relevant bus options, renaming them
>>consistently with that, and making the bus options components.
>
>
> I brief check it and got a compile error. There are two undefined CDL
> names: cdl_option CYGNUM_IO_SPI_ARM_LPC2XXX_BUS{0,1}_INTPRIO instead
> SPI{0,1}. It looks like a copy & paste typo. I prefer no Changelog
> this. Fix it, please.
It should have been the other way round to make the option named
consistently with its parent. Fixed anyway.
Jifl
--
*See us at Embedded World 2009, Nürnberg, Germany, 3-5 Mar, Stand 11-300*
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
next prev parent reply other threads:[~2009-02-17 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 9:57 Sergei Gavrikov
2009-02-17 0:54 ` Jonathan Larmour
2009-02-17 7:38 ` Sergei Gavrikov
2009-02-17 9:09 ` Jonathan Larmour [this message]
2009-02-17 10:19 ` Sergei Gavrikov
2009-02-18 17:30 ` Jonathan Larmour
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=499A7EE3.9000502@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-patches@ecos.sourceware.org \
--cc=sg@belvok.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).