public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>, Changli Gao <xiaosuo@gmail.com>,
	linux-next@vger.kernel.org
Subject: Re: Fw: [PATCH] drm: build error when magic sysrq isn't enabled
Date: Wed, 31 Mar 2010 09:53:22 -0700	[thread overview]
Message-ID: <20100331095322.48b94afd.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100331172157.12be4cce.sfr@canb.auug.org.au>

On Wed, 31 Mar 2010 17:21:57 +1100 Stephen Rothwell wrote:

> Hi Dave,
> 
> One for you?

Did this patch not work or was it not applied/tested?
http://lkml.org/lkml/2010/3/25/315

Also 2 other SYSRQ patches that day:

http://lkml.org/lkml/2010/3/25/314
http://lkml.org/lkml/2010/3/25/316


> Begin forwarded message:
> 
> Date: Wed, 31 Mar 2010 12:18:00 +0800
> From: Changli Gao <xiaosuo@gmail.com>
> To: linux-next@vger.kernel.org
> Cc: xiaosuo <xiaosuo@gmail.com>
> Subject: [PATCH] drm: build error when magic sysrq isn't enabled
> 
> 
> drm build error when magic sysrq isn't enabled
> 
> sysrq_drm_fb_helper_restore_op is only valid when magic sysrq is
> enabled, but it is used whenever magic sysrq is enabled or not.
> 
> Signed-off-by: Changli Gao <xiaosuo@gmail.com>
> ----
> drivers/gpu/drm/drm_fb_helper.c | 4 ++++
> 1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
> index 85cdf05..0e5b4f6 100644
> --- a/drivers/gpu/drm/drm_fb_helper.c
> +++ b/drivers/gpu/drm/drm_fb_helper.c
> @@ -913,7 +913,9 @@ int drm_fb_helper_single_fb_probe(struct drm_device *dev,
>  		printk(KERN_INFO "registered panic notifier\n");
>  		atomic_notifier_chain_register(&panic_notifier_list,
>  					       &paniced);
> +#ifdef CONFIG_MAGIC_SYSRQ
>  		register_sysrq_key('v', &sysrq_drm_fb_helper_restore_op);
> +#endif
>  	}
>  	list_add(&fb_helper->kernel_fb_list, &kernel_fb_helper_list);
>  	return 0;
> @@ -927,7 +929,9 @@ void drm_fb_helper_free(struct drm_fb_helper *helper)
>  		printk(KERN_INFO "unregistered panic notifier\n");
>  		atomic_notifier_chain_unregister(&panic_notifier_list,
>  						 &paniced);
> +#ifdef CONFIG_MAGIC_SYSRQ
>  		unregister_sysrq_key('v', &sysrq_drm_fb_helper_restore_op);
> +#endif
>  	}
>  	drm_fb_helper_crtc_free(helper);
>  	fb_dealloc_cmap(&helper->fb->fbdev->cmap);
> 
> 
> -- 


---
~Randy

  reply	other threads:[~2010-03-31 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  6:21 Fw: [PATCH] drm: build error when magic sysrq isn't enabled Stephen Rothwell
2010-03-31 16:53 ` Randy Dunlap [this message]
2010-03-31 20:58   ` Dave Airlie

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=20100331095322.48b94afd.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=airlied@linux.ie \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=xiaosuo@gmail.com \
    /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