From: Andrew Morton <akpm@zip.com.au>
To: "Michael C. Toren" <mct@toren.net>
Cc: linux-kernel@vger.kernel.org, Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: acquire_console_sem exported, but not release_console_sem?
Date: Sat, 12 Jan 2002 19:36:04 -0800 [thread overview]
Message-ID: <3C4100A4.2EDA7410@zip.com.au> (raw)
In-Reply-To: <20020112215402.A3254@quint.netisland.net>
"Michael C. Toren" wrote:
>
> Hi,
>
> In kernel/printk.c, it looks like acquire_console_sem() is exported, but
> not release_console_sem()? Is this intentional, or just an oversight?
Oversight. It's possible that some modular video drivers will need
to acquire this lock, so it should be exported. At this time, it's
only fbcon.c and that code doesn't support modular linkage, so
nobody has noticed.
--- linux-2.4.18-pre3/kernel/printk.c Thu Jan 10 13:39:50 2002
+++ linux-akpm/kernel/printk.c Sat Jan 12 19:32:50 2002
@@ -529,6 +529,7 @@ void release_console_sem(void)
if (must_wake_klogd && !oops_in_progress)
wake_up_interruptible(&log_wait);
}
+EXPORT_SYMBOL(release_console_sem);
/** console_conditional_schedule - yield the CPU if required
*
prev parent reply other threads:[~2002-01-13 3:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 2:54 acquire_console_sem exported, but not release_console_sem? Michael C. Toren
2002-01-13 3:36 ` Andrew Morton [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=3C4100A4.2EDA7410@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mct@toren.net \
/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