public inbox for ecos-cvs@sourceware.org
help / color / mirror / Atom feed
From: asl@sourceware.org
To: ecos-cvs@ecos.sourceware.org
Subject: ecos/packages/devs/serial/arm/at91/current Cha ...
Date: Thu, 11 Nov 2004 08:57:00 -0000 [thread overview]
Message-ID: <20041111085744.9915.qmail@sourceware.org> (raw)
CVSROOT: /cvs/ecos
Module name: ecos
Changes by: asl@sourceware.org 2004-11-11 08:57:43
Modified files:
packages/devs/serial/arm/at91/current: ChangeLog
packages/devs/serial/arm/at91/current/cdl: ser_arm_at91.cdl
packages/devs/serial/arm/at91/current/src: at91_serial.c
Log message:
* src/at91_serial.c: Added third port
next reply other threads:[~2004-11-11 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 8:57 asl [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-02 17:20 asl
2006-03-13 7:46 asl
2006-03-01 18:13 asl
2006-02-19 19:52 asl
2004-01-26 8:38 asl
2003-11-21 19:06 gthomas
2003-11-20 21:28 asl
2003-10-16 18:02 nickg
2003-02-24 14:12 jlarmour
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=20041111085744.9915.qmail@sourceware.org \
--to=asl@sourceware.org \
--cc=ecos-cvs@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).