From: Jeff Dike <jdike@addtoit.com>
To: alessandro salvatori <sandr8@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH 10/19] UML - Remove spinlock wrapper functions
Date: Fri, 4 Aug 2006 10:14:47 -0400 [thread overview]
Message-ID: <20060804141447.GA3837@ccure.user-mode-linux.org> (raw)
In-Reply-To: <517e86fb0608040600n52f36b8ci60f4e219f8cd4b5a@mail.gmail.com>
On Fri, Aug 04, 2006 at 01:00:43PM +0000, alessandro salvatori wrote:
> the new lock irq_lock is still static, but we now have preprocessor
> macros to be included from a header file instead of non-static functions in
> the same module as the static irq_lock.
I don't understand. The changes in this patch are -
remove two functions and their declarations
replace calls to those functions with spin_lock_irq_save and
spin_unlock_irqsave
move the spinlock declaration above the spin_(un)lock_irq_save
calls
Which of these are you talking about?
Jeff
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Dike <jdike@addtoit.com>
To: alessandro salvatori <sandr8@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH 10/19] UML - Remove spinlock wrapper functions
Date: Fri, 4 Aug 2006 10:14:47 -0400 [thread overview]
Message-ID: <20060804141447.GA3837@ccure.user-mode-linux.org> (raw)
In-Reply-To: <517e86fb0608040600n52f36b8ci60f4e219f8cd4b5a@mail.gmail.com>
On Fri, Aug 04, 2006 at 01:00:43PM +0000, alessandro salvatori wrote:
> the new lock irq_lock is still static, but we now have preprocessor
> macros to be included from a header file instead of non-static functions in
> the same module as the static irq_lock.
I don't understand. The changes in this patch are -
remove two functions and their declarations
replace calls to those functions with spin_lock_irq_save and
spin_unlock_irqsave
move the spinlock declaration above the spin_(un)lock_irq_save
calls
Which of these are you talking about?
Jeff
next prev parent reply other threads:[~2006-08-04 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 0:33 [uml-devel] [PATCH 10/19] UML - Remove spinlock wrapper functions Jeff Dike
2006-07-07 0:33 ` Jeff Dike
2006-08-04 13:00 ` [uml-devel] " alessandro salvatori
2006-08-04 13:02 ` alessandro salvatori
2006-08-04 14:14 ` Jeff Dike [this message]
2006-08-04 14:14 ` Jeff Dike
2006-08-05 11:47 ` Blaisorblade
2006-08-05 11:47 ` Blaisorblade
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=20060804141447.GA3837@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandr8@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.