All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] About Mark's advice on bug 48
Date: Mon Mar 29 14:13:16 2004	[thread overview]
Message-ID: <20040329201311.GU10672@ca-server1.us.oracle.com> (raw)
In-Reply-To: <4063E97B.7020100@intel.com>

On Fri, Mar 26, 2004 at 04:27:39PM +0800, Sonic Zhang wrote:
> Hi Mark,
> 
> Yes, I find the code in ocfs_daemonize() to allow kernel thread to 
> receive signals. So, I change the signal process code to make it 
> compilable under kernel 2.6. Please check my revise.
Ahh, ok the 2.6 compatibility stuff I definitely missed. I'll commit the
change with that in it. Thanks for testing / revising this.
	--Mark

--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com

  reply	other threads:[~2004-03-29 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26  1:26 [Ocfs2-devel] About Mark's advice on bug 48 Sonic Zhang
2004-03-26  2:27 ` Sonic Zhang
2004-03-29 14:13   ` Mark Fasheh [this message]
2004-03-29 14:28 ` Mark Fasheh
  -- strict thread matches above, loose matches on Subject: below --
2004-03-25  3:26 Sonic Zhang
2004-03-25 13:10 ` Mark Fasheh

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=20040329201311.GU10672@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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 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.