From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] unexport panic_timeout
Date: Sat, 23 Apr 2005 16:56:09 -0700 [thread overview]
Message-ID: <20050423165609.47087f9a.akpm@osdl.org> (raw)
In-Reply-To: <20050415151048.GL5456@stusta.de>
Adrian Bunk <bunk@stusta.de> wrote:
>
> I didn't find any possible modular usage in the kernel.
>
panic_timeout has many in-kernel users and it is used from within a module
in 2.4.30.
Hence it is easily possible that some out-of-tree code is dependent upon
this export, hence I shan't be applying this patch.
>
> --- linux-2.6.11-rc5-mm1-full/kernel/panic.c.old 2005-03-04 00:54:46.000000000 +0100
> +++ linux-2.6.11-rc5-mm1-full/kernel/panic.c 2005-03-04 00:54:54.000000000 +0100
> @@ -24,8 +24,6 @@
> int panic_on_oops;
> int tainted;
>
> -EXPORT_SYMBOL(panic_timeout);
> -
> struct notifier_block *panic_notifier_list;
>
> EXPORT_SYMBOL(panic_notifier_list);
next prev parent reply other threads:[~2005-04-23 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 15:10 [2.6 patch] unexport panic_timeout Adrian Bunk
2005-04-23 23:56 ` Andrew Morton [this message]
2005-05-02 1:46 ` [2.6 patch] __deprecated_for_modules panic_timeout Adrian Bunk
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=20050423165609.47087f9a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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