From: Stephen Williams <gfi8d1h02@sneakemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] SystemACE support for u-boot via fat
Date: Mon, 09 Feb 2004 16:29:55 -0800 [thread overview]
Message-ID: <13853-75826@sneakemail.com> (raw)
In-Reply-To: <20040209234337.82F8EC1215@atlas.denx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wolfgang Denk wd-at-denx.de |u-boot-users| wrote:
| In message <29498-57591@sneakemail.com> you wrote:
|
|>This is the systemace.h and systemace.c files that goes
|>with the earlier posted systemace patch. These files go
|>in include/systemace.h and common/cmd_ace.c
|>
|>--------------------------
|>#ifndef __systemace_H
|>#define __systemace_H
|>/*
|
|
| Sorry, this format is not acceptable. Please submit a proper patch.
| See section "Submitting Patches" in the README.
|
|
| There is NO need to handle new files differently (the 'N' option to
| diff will take care of that). And please do not include any releavant
| text (patches, files) _inline_ if you are not 100% sure that your
| mailer does not wrap lines.
"cvs diff -puRN" does not include new files, the -N flag is
useless in that context as cvs does not know of those files
so does not even try to diff them. You will need to accept
the patch (made outside of CVS) then do a "cvs add" so that
they are added to the repository.
As for inline vs. attachment, many lists don't accept attachments,
so I was being cautious. However, the README does explicitly
say that MINE attachments are accepted. Oh well.
* Add support for Xilinx SystemACE chip:
~ New file common/cmd_ace.c
~ New file include/systemace.h
~ Hook systemace support into cmd_fat and the partition manager.
- --
Steve Williams "The woods are lovely, dark and deep.
steve at XXXXXXXXXX But I have promises to keep,
http://www.XXXXXXXXXX and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAKCYCrPt1Sc2b3ikRAqj9AKC0tH2WJvp5FhuorqaN/3wUyXNSxgCg6/Eb
K8fRbPSyqZ/TeUbkKSDbw+Q=
=YU/H
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ace.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20040209/726ead92/attachment.txt
next prev parent reply other threads:[~2004-02-10 0:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040205092533.1FC23C10A3@atlas.denx.de>
2004-02-05 17:29 ` [U-Boot-Users] SystemACE support for u-boot via fat Stephen Williams
2004-02-09 23:44 ` Wolfgang Denk
2004-02-05 17:33 ` Stephen Williams
2004-02-09 23:43 ` Wolfgang Denk
2004-02-10 0:29 ` Stephen Williams [this message]
2004-02-10 8:41 ` Stephan Linz
2004-02-10 17:52 ` Stephen Williams
2004-02-10 22:22 ` Wolfgang Denk
2004-02-23 0:05 ` Wolfgang Denk
2004-02-10 18:09 Demke, Torsten
2004-02-10 18:18 ` Stephen Williams
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 2:53 Stephen Williams
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=13853-75826@sneakemail.com \
--to=gfi8d1h02@sneakemail.com \
--cc=u-boot@lists.denx.de \
/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