From: Mazen Arakji <mazenarakji@aim.com>
To: dev@mynewt.apache.org, info@chibios.org,
canoncustomersupport@cusa.canon.com, questions@rowebots.com,
ecos-maintainers@ecos.sourceware.org, info@enea.com,
admin@evidence.eu.com, info@freertos.org,
info@highintegritysystems.com, info@ghs.com,
info@intervalzero.com, kingstarsales@kingstar.com,
info@tenasys.com, inside@lynx.com, info@weston-embedded.com,
info@nxp.com, tech.support@nxp.com, info@nokia-bell-labs.com,
info@nokia.com, info@DigitalResearch.biz, contact@siemens.com,
dev@nuttx.apache.org, info@altreonic.com, info@avaya.com,
info@microware.com, niisi@niisi.msk.ru, dz@dz.ru,
contact@phoenix-rtos.com, info@sysgo.com, info@px5rtos.com,
info@blackberry.com, info@state-machine.com, devel@riot-os.org,
support@rt-thread.com, roberto.bucher@supsi.ch,
lorenzo.dozio@polimi.it, devel@rtems.org, info@intervalzero.com,
info@quadros.com, juniper-info@juniper.net,
shark-help@gandalf.sssup.it, mail@miray.de, info@ibm.com,
csosoft@us.ibm.com, fednotes@us.ibm.com, office@tron.org,
inquiries@windriver.com, csiroenquiries@csiro.au,
xenomai@lists.linux.dev, main@lists.zephyrproject.org,
devel@lists.zephyrproject.org
Subject: Patent Infringement Notice
Date: Sun, 12 Nov 2023 06:55:14 +0000 (UTC) [thread overview]
Message-ID: <797142864.1347764.1699772114971@mail.yahoo.com> (raw)
In-Reply-To: 797142864.1347764.1699772114971.ref@mail.yahoo.com
Do not, in the United States, benefit from an RTOS that does not proceed to disable interrupts in order to insert a task into a collection of tasks.
If you do, you will owe me money.
Mazen Arakji
next parent reply other threads:[~2023-11-12 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <797142864.1347764.1699772114971.ref@mail.yahoo.com>
2023-11-12 6:55 ` Mazen Arakji [this message]
[not found] ` <1641995453.1340205.1699772516422@mail.yahoo.com>
[not found] ` <1811697794.1339066.1699773777919@mail.yahoo.com>
2023-11-12 14:49 ` STOP Quantum Leaps
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=797142864.1347764.1699772114971@mail.yahoo.com \
--to=mazenarakji@aim.com \
--cc=admin@evidence.eu.com \
--cc=canoncustomersupport@cusa.canon.com \
--cc=contact@phoenix-rtos.com \
--cc=contact@siemens.com \
--cc=csiroenquiries@csiro.au \
--cc=csosoft@us.ibm.com \
--cc=dev@mynewt.apache.org \
--cc=dev@nuttx.apache.org \
--cc=devel@lists.zephyrproject.org \
--cc=devel@riot-os.org \
--cc=devel@rtems.org \
--cc=dz@dz.ru \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=fednotes@us.ibm.com \
--cc=info@DigitalResearch.biz \
--cc=info@altreonic.com \
--cc=info@avaya.com \
--cc=info@blackberry.com \
--cc=info@chibios.org \
--cc=info@enea.com \
--cc=info@freertos.org \
--cc=info@ghs.com \
--cc=info@highintegritysystems.com \
--cc=info@ibm.com \
--cc=info@intervalzero.com \
--cc=info@microware.com \
--cc=info@nokia-bell-labs.com \
--cc=info@nokia.com \
--cc=info@nxp.com \
--cc=info@px5rtos.com \
--cc=info@quadros.com \
--cc=info@state-machine.com \
--cc=info@sysgo.com \
--cc=info@tenasys.com \
--cc=info@weston-embedded.com \
--cc=inquiries@windriver.com \
--cc=inside@lynx.com \
--cc=juniper-info@juniper.net \
--cc=kingstarsales@kingstar.com \
--cc=lorenzo.dozio@polimi.it \
--cc=mail@miray.de \
--cc=main@lists.zephyrproject.org \
--cc=niisi@niisi.msk.ru \
--cc=office@tron.org \
--cc=questions@rowebots.com \
--cc=roberto.bucher@supsi.ch \
--cc=shark-help@gandalf.sssup.it \
--cc=support@rt-thread.com \
--cc=tech.support@nxp.com \
--cc=xenomai@lists.linux.dev \
/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).