public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Wessel <jason.wessel@windriver•com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail•com>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the kgdb tree
Date: Fri, 21 May 2010 11:09:38 +1000	[thread overview]
Message-ID: <20100521110938.7bbbbf59.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4BF5D8AF.6010408@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

Hi Jason,

On Thu, 20 May 2010 19:49:51 -0500 Jason Wessel <jason.wessel@windriver•com> wrote:
>
> Before brute force toggling it, it seems we should check the value and
> restore it after the execution of handle_sysrq().

Indeed, at the time I couldn't find an easy way to do that.

> I'll have to look and see if there is an access function for this.

Great, thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-05-21  1:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23  4:04 linux-next: build failure after merge of the kgdb tree Stephen Rothwell
2010-03-25  4:43 ` Stephen Rothwell
2010-03-25  4:59   ` Dmitry Torokhov
2010-05-21  0:21     ` Stephen Rothwell
2010-05-21  0:49       ` Jason Wessel
2010-05-21  1:09         ` Stephen Rothwell [this message]
2010-05-21  1:23           ` Dmitry Torokhov
2010-05-21  1:28             ` Jason Wessel
2010-05-24 18:17               ` Dmitry Torokhov
2010-05-24 20:04                 ` Jason Wessel
2010-05-24 20:34                   ` Dmitry Torokhov
2010-05-24 20:50                     ` Jason Wessel
  -- strict thread matches above, loose matches on Subject: below --
2020-05-19 14:05 Stephen Rothwell
2020-05-19 14:58 ` Doug Anderson
2020-05-19 15:52   ` Doug Anderson

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=20100521110938.7bbbbf59.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=dmitry.torokhov@gmail$(echo .)com \
    --cc=jason.wessel@windriver$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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