From: John Dallaway <john@dallaway.org.uk>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: eCos Patches <ecos-patches@ecos.sourceware.org>,
Christophe Coutand <ccoutand@stmi.com>
Subject: Re: AT91 ADC support
Date: Sat, 29 May 2010 13:10:00 -0000 [thread overview]
Message-ID: <4C011221.9040205@dallaway.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1005291302520.14094@sg-laptop>
Hi Sergei
Sergei Gavrikov wrote:
> Excuse, that took a bit more time for testing. So, with the latest sent
> stuff, it's possible to build ADC driver and ADC tests for the next AT91
> targets
>
> at91sam7sek: SUCCESS
> at91sam7xek: SUCCESS
> sam7ex256: SUCCESS
> eb55: SUCCESS
> phycore: SUCCESS
>
> I'm personally do not see any pit stops which would block a check-in the
> latest version of the driver. Christophe, thank you for your time and
> contribution. John?
I have no objections. My concern was that we avoid an unquantified delay
in checking-in Christophe's contribution.
Thank you for sorting this out...
John Dallaway
eCos maintainer
next prev parent reply other threads:[~2010-05-29 13:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 9:40 Christophe Coutand
2010-05-27 13:42 ` John Dallaway
2010-05-27 13:52 ` Sergei Gavrikov
2010-05-27 14:16 ` Christophe Coutand
2010-05-27 14:47 ` John Dallaway
2010-05-27 15:44 ` Christophe Coutand
2010-05-27 16:08 ` John Dallaway
2010-05-27 16:37 ` Kurt Siedenburg
2010-05-27 16:37 ` Sergei Gavrikov
2010-05-27 19:49 ` Christophe Coutand
2010-05-27 21:44 ` Sergei Gavrikov
2010-05-29 10:24 ` Sergei Gavrikov
2010-05-29 13:10 ` John Dallaway [this message]
2010-05-30 10:34 ` Sergei Gavrikov
2010-05-30 12:40 ` Christophe Coutand
2010-05-30 13:46 ` Sergei Gavrikov
2011-02-22 11:33 ` John Dallaway
2010-05-27 21:37 ` Christophe Coutand
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=4C011221.9040205@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ccoutand@stmi.com \
--cc=ecos-patches@ecos.sourceware.org \
--cc=sergei.gavrikov@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).