From: Zach Brown <zach.brown@oracle.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
mark.fasheh@oracle.com, kurt.hackel@oracle.com
Subject: Re: Question re: __mlog_cpu_guess in fs/ocfs2/cluster/masklog.h
Date: Tue, 23 May 2006 09:42:50 -0700 [thread overview]
Message-ID: <44733B8A.40807@oracle.com> (raw)
In-Reply-To: <1148402074.12529.65.camel@mindpipe>
> I was wondering how it could not be a bug to use smp_processor_id in
> preemptible code, but I see that it's only used for debug output. Sorry
> for the noise.
No problem, thanks for taking a look in the first place. We'll update
the comment to make it more explicit.
- z
prev parent reply other threads:[~2006-05-23 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 23:45 Question re: __mlog_cpu_guess in fs/ocfs2/cluster/masklog.h Lee Revell
2006-05-23 15:27 ` Zach Brown
2006-05-23 16:34 ` Lee Revell
2006-05-23 16:42 ` Zach Brown [this message]
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=44733B8A.40807@oracle.com \
--to=zach.brown@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=rlrevell@joe-job.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