From: "Randy.Dunlap" <rddunlap@osdl.org>
To: mingo@redhat.com, torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] fix Documentation/cli-sti-removal.txt thinko
Date: Mon, 17 Feb 2003 13:30:28 -0800 [thread overview]
Message-ID: <20030217133028.4fd505f2.rddunlap@osdl.org> (raw)
Hi,
Please apply to 2.5.61.
The 3 lines being deleted are repeated from above (in same file).
I pulled the 2 lines being added from an earlier version of the patch.
--
~Randy
patch_name: cli-fixdoc.patch
patch_version: 2003-02-17.13:15:29
author: Randy.Dunlap <rddunlap@osdl.org>
description: correct cli-sti-removal.txt cut-n-paste'os
product: Linux
product_versions: linux-2561
changelog: _
URL: _
requires: _
conflicts: _
diffstat: =
cli-sti-removal.txt | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff -Naur ./Documentation/cli-sti-removal.txt%CLI ./Documentation/cli-sti-removal.txt
--- ./Documentation/cli-sti-removal.txt%CLI Fri Feb 14 15:51:21 2003
+++ ./Documentation/cli-sti-removal.txt Mon Feb 17 13:15:09 2003
@@ -121,9 +121,8 @@
another related change is that synchronize_irq() now takes a parameter:
synchronize_irq(irq). This change too has the purpose of making SMP
-to make the transition easier, we've still kept the cli(), sti(),
-save_flags() and restore_flags() macros defined on UP systems - but
-their usage will be phased out until the 2.6 kernel is released.
+synchronization more lightweight - this way you can wait for your own
+interrupt handler to finish, no need to wait for other IRQ sources.
why were these changes done? The main reason was the architectural burden
reply other threads:[~2003-02-17 21:23 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=20030217133028.4fd505f2.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®