All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jcromie@domain.hid>
To: adeos-main@gna.org, Philippe Gerum <rpm@xenomai.org>
Subject: [Adeos-main] [patch]  spelling errors - s/prioritary/priority/
Date: Mon, 14 Mar 2005 07:33:33 -0700	[thread overview]
Message-ID: <4235A0BD.2010601@domain.hid> (raw)

[-- Attachment #1: Type: text/plain, Size: 251 bytes --]

hi Philippe,

attached patch fixes spelling in adeos r9c6 patch;
prioritary -> priority.
I resisted urge to tinker with sentences around them;
I didnt want to subtly alter the meaning of stuff I dont
understand.

hth, and thanks for your work.
jimc



[-- Attachment #2: c6.patch --]
[-- Type: text/plain, Size: 3622 bytes --]

--- adeos-linux-2.6.10-i386-r9c6.patch.orig	2005-03-13 22:24:51.000000000 -0700
+++ adeos-linux-2.6.10-i386-r9c6.patch	2005-03-14 06:24:15.611540350 -0700
@@ -701,7 +701,7 @@
 +
 +    /* Make the current domain (== sleeper) wait for the mutex to be
 +       released. Adeos' pipelined scheme guarantees that the new
-+       sleeper _is_ more prioritary than any aslept domain since we
++       sleeper _is_ more priority than any aslept domain since we
 +       have stalled each sleeper's stage. Must be called with local hw
 +       interrupts off. */
 +
@@ -734,7 +734,7 @@
 +    flags = __test_and_set_bit(IPIPE_STALL_FLAG,&adp->cpudata[cpuid].status);
 +
 +    /* Two cases to handle here on SMP systems, only one for UP:
-+       1) in case of a conflicting access from a prioritary domain
++       1) in case of a conflicting access from a priority domain
 +       running on the same cpu, make this domain sleep on the mutex,
 +       and resume the current owner so it can release the lock asap.
 +       2) in case of a conflicting access from any domain on a
@@ -797,7 +797,7 @@
 +    if (mutex->sleepq != NULL)
 +	{
 +	adomain_t *sleeper = mutex->sleepq;
-+	/* Wake up the first most prioritary sleeper. */
++	/* Wake up the first highest priority sleeper. */
 +	mutex->sleepq = sleeper->m_link;
 +	__adeos_switch_to(adp_cpu_current[cpuid],sleeper,cpuid);
 +	adeos_load_cpuid();
@@ -2225,7 +2225,7 @@
 +	    if (adp == adp_root)
 +		{
 +		/* Make sure to re-enable hw interrupts to reduce
-+		   preemption latency by more prioritary domains when
++		   preemption latency by more priority domains when
 +		   calling Linux handlers. */
 +
 +		adeos_hw_sti();
@@ -2401,8 +2401,8 @@
 +       in mind that domains having a higher priority than the current
 +       one are sleeping on the adeos_suspend_domain() service. In
 +       addition, domains having a lower priority have been preempted
-+       by an interrupt dispatched to a more prioritary domain. Once
-+       the first and most prioritary stage has been selected here, the
++       by an interrupt dispatched to a more priority domain. Once
++       the first and highest priority stage has been selected here, the
 +       subsequent stages will be activated in turn when each visited
 +       domain calls adeos_suspend_domain() to wake up its neighbour
 +       down the pipeline. */
@@ -2419,7 +2419,7 @@
 +   just like if it has been actually received from a hw source. This
 +   both works for real and virtual interrupts. This also means that
 +   the current domain might be immediately preempted by a more
-+   prioritary domain who happens to handle this interrupt. */
++   priority domain who happens to handle this interrupt. */
 +
 +int fastcall adeos_trigger_irq (unsigned irq)
 +
@@ -5245,7 +5245,7 @@
 +   in the pipeline will get a chance to process the event. The latter
 +   will eventually be allowed to process its own event too if a valid
 +   handler exists for it.  Handler executions are always scheduled by
-+   the domain which raised the event for the prioritary domains
++   the domain which raised the event for the priority domains
 +   wanting to be notified of such event.  Note: evdata might be
 +   NULL. */
 +
@@ -5289,7 +5289,7 @@
 +	    next_domain->cpudata[cpuid].event_info.propagate = 0;
 +	    __set_bit(IPIPE_XPEND_FLAG,&next_domain->cpudata[cpuid].status);
 +
-+	    /* Let the prioritary domain process the event. */
++	    /* Let the priority domain process the event. */
 +	    __adeos_switch_to(this_domain,next_domain,cpuid);
 +	    
 +	    adeos_load_cpuid();	/* Processor might have changed. */

             reply	other threads:[~2005-03-14 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 14:33 Jim Cromie [this message]
2005-03-15  7:56 ` [Adeos-main] [patch] spelling errors - s/prioritary/priority/ Philippe Gerum

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=4235A0BD.2010601@domain.hid \
    --to=jcromie@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=rpm@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.