From: Wakko Warner <wakko@animx.eu.org>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Re: Oops on megaraid.
Date: Wed, 5 Jan 2005 17:33:20 -0500 [thread overview]
Message-ID: <20050105223320.GA7622@animx.eu.org> (raw)
In-Reply-To: <20050105180457.GK26051@parcelfarce.linux.theplanet.co.uk>
Al Viro wrote:
> Someone's removing non-empty directory in procfs. Let's see...
> Indeed.
> #ifdef CONFIG_PROC_FS
> remove_proc_entry("megaraid", &proc_root);
> #endif
>
> pci_unregister_driver(&megaraid_pci_driver);
> so we remove /proc/megaraid and then procees to remove controllers found
> by driver. Each of those has a subdirectory in /proc/megaraid...
>
> Fix is trivial:
Cool, thanks.
--
Lab tests show that use of micro$oft causes cancer in lab animals
prev parent reply other threads:[~2005-01-05 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050105174752.GA6859@animx.eu.org>
2005-01-05 18:04 ` [PATCH] Re: Oops on megaraid Al Viro
2005-01-05 22:33 ` Wakko Warner [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=20050105223320.GA7622@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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