From: Stephen Polkowski <stephen@centtech.com>
To: ecos-maintainers@ecos.sourceware.org
Subject: Question regarding patches
Date: Thu, 30 Jun 2011 20:31:00 -0000 [thread overview]
Message-ID: <4E0CDCD8.3000202@centtech.com> (raw)
Hello Maintainers,
I submitted a patch about a week ago for the Via Rhine (10/100) driver [1001269].
There was a small bug that required a simple fix. I listed the patch under Ethernet,
but now I'm wondering if I should have listed it under "Patches and Contributions"?
Am I following the correct procedures to get this patch into the CVS tree?
How long does it usually take to get a change into CVS? The reason I ask is that I'm
planning a REDBOOT rhine package for IA32. I already have it working my office. I
just wanted to see how my simple Rhine patch worked out before submitting a REDBOOT
rhine package.
Ultimately, I want to release a new Via Velocity (Gigabit) ethernet driver for eCos.
So, I'm getting my feet wet with some small changes first.
Thanks in advance,
Stephen
--
Stephen Polkowski
Centaur Technology
VIA Technologies, Inc
next reply other threads:[~2011-06-30 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 20:31 Stephen Polkowski [this message]
2011-06-30 20:59 ` John Dallaway
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=4E0CDCD8.3000202@centtech.com \
--to=stephen@centtech.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).