From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: Cavium Octeon (new architecture in OpenBSD); from jmc@.
Date: Tue, 26 Mar 2013 20:19:27 -0400 (EDT) [thread overview]
Message-ID: <201303270019.r2R0JRCR008942@krisdoz.my.domain> (raw)
Log Message:
-----------
Cavium Octeon (new architecture in OpenBSD); from jmc@.
Modified Files:
--------------
mdocml:
arch.in
Revision Data
-------------
Index: arch.in
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/arch.in,v
retrieving revision 1.12
retrieving revision 1.13
diff -Larch.in -Larch.in -u -p -r1.12 -r1.13
--- arch.in
+++ arch.in
@@ -81,6 +81,7 @@ LINE("netwinder", "NetWinder")
LINE("news68k", "NeWS68k")
LINE("newsmips", "NeWSMIPS")
LINE("next68k", "NeXT68k")
+LINE("octeon", "OCTEON")
LINE("ofppc", "OFPPC")
LINE("palm", "Palm")
LINE("pc532", "PC532")
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2013-03-27 0:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201303270019.r2R0JRCR008942@krisdoz.my.domain \
--to=schwarze@mdocml.bsd.lv \
--cc=source@mdocml.bsd.lv \
/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 NNTP newsgroup(s).