From: Gary Thomas <gary@mlbassoc.com>
To: "Choi, David" <David.Choi@Micrel.Com>
Cc: "Li, Charles" <Charles.Li@Micrel.Com>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: ks8851_mll driver at eCos
Date: Wed, 21 Apr 2010 18:01:00 -0000 [thread overview]
Message-ID: <4BCF3D52.2020709@mlbassoc.com> (raw)
In-Reply-To: <C43529A246480145B0A6D0234BDB0F0D481CF0@MELANITE.micrel.com>
On 04/21/2010 11:35 AM, Choi, David wrote:
> Hello Gary,
>
> I get your information after submitting my driver at eCos community a
> couple of days ago.
>
> This is my first time submitting my source code to eCos. So still I am
> in the learning curve in the eCos world.
>
> If you have time, please take a look at it and give me feedback.
First glance, it looks pretty good. Some cleanup will need to be done:
* Please test & submit against the "current" (anonymous CVS) tree
* The copyright boilerplate in each file needs to be updated to
match the new FSF style (refer to the CVS tree)
>
> By the way, a couple of month ago, I sent an email, which I believe
> triggers FSF sending [copywrite assignment document].
>
> Until today, I have not received any document about it. I want to know
> the status but I donÂ’t know how to trace it.
I've no clue, sorry. Perhaps one of the other maintainers can help?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next parent reply other threads:[~2010-04-21 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C43529A246480145B0A6D0234BDB0F0D481CF0@MELANITE.micrel.com>
2010-04-21 18:01 ` Gary Thomas [this message]
2010-04-21 18:36 ` 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=4BCF3D52.2020709@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=Charles.Li@Micrel.Com \
--cc=David.Choi@Micrel.Com \
--cc=ecos-maintainers@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).