From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [ PATCH ] Longhaul - call suspend(PMSG_FREEZE) before and resume() after
Date: Sat, 27 May 2006 17:32:49 -0400 [thread overview]
Message-ID: <20060527213249.GA5366@redhat.com> (raw)
In-Reply-To: <4478640A.2030001@interia.pl>
On Sat, May 27, 2006 at 04:36:58PM +0200, Rafał Bilski wrote:
Because of this chunk..
> diff -uprN -X linux-2.6.16.18-vanilla/Documentation/dontdiff linux-2.6.16.18-vanilla/block/genhd.c linux-2.6.16.18/block/genhd.c
> --- linux-2.6.16.18-vanilla/block/genhd.c 2006-05-27 15:50:01.000000000 +0200
> +++ linux-2.6.16.18/block/genhd.c 2006-05-27 15:53:13.000000000 +0200
> @@ -16,9 +16,9 @@
> #include <linux/kobj_map.h>
> #include <linux/buffer_head.h>
>
> -static struct subsystem block_subsys;
> +struct subsystem block_subsys;
>
> -static DECLARE_MUTEX(block_subsys_sem);
> +DECLARE_MUTEX(block_subsys_sem);
>
> /*
> * Can be deleted altogether. Later.
> @@ -511,8 +511,10 @@ static struct kset_uevent_ops block_ueve
> };
>
> /* declare block_subsys. */
> -static decl_subsys(block, &ktype_block, &block_uevent_ops);
> +decl_subsys(block, &ktype_block, &block_uevent_ops);
>
> +EXPORT_SYMBOL(block_subsys);
> +EXPORT_SYMBOL(block_subsys_sem);
This really should also get posted to linux-kernel, though I don't
think people are going to be particularly enthusiastic about exposing
these innards to modules.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-05-27 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 14:36 [ PATCH ] Longhaul - call suspend(PMSG_FREEZE) before and resume() after Rafał Bilski
2006-05-27 21:29 ` Benjamin Herrenschmidt
2006-05-27 21:32 ` Dave Jones [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=20060527213249.GA5366@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=rafalbilski@interia.pl \
/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