From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: unionfs@filesystems.org, linux-fsdevel@vger.kernel.org,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] unionfs: sioq not __exit
Date: Mon, 19 Mar 2007 19:20:07 -0400 [thread overview]
Message-ID: <20070319232007.GA25181@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <20070319152226.075c83e1.randy.dunlap@oracle.com>
On Mon, Mar 19, 2007 at 03:22:26PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> stop_sioq() is called from both __init and __exit functions, so it
> shouldn't be marked __exit.
>
> Reported on the kernelnewbies mailing list, but no patch offered there.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Applied.
Thanks.
Josef "Jeff" Sipek.
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan
prev parent reply other threads:[~2007-03-19 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 22:22 [PATCH] unionfs: sioq not __exit Randy Dunlap
2007-03-19 23:20 ` Josef Sipek [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=20070319232007.GA25181@filer.fsl.cs.sunysb.edu \
--to=jsipek@fsl.cs.sunysb.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=unionfs@filesystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).