From: Jason Wessel <jason.wessel@windriver•com>
To: Dmitry Torokhov <dmitry.torokhov@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the kgdb tree
Date: Mon, 24 May 2010 15:50:04 -0500 [thread overview]
Message-ID: <4BFAE67C.6080000@windriver.com> (raw)
In-Reply-To: <201005241334.04277.dmitry.torokhov@gmail.com>
On 05/24/2010 03:34 PM, Dmitry Torokhov wrote:
> On Monday 24 May 2010 01:04:17 pm Jason Wessel wrote:
>
>> On 05/24/2010 01:17 PM, Dmitry Torokhov wrote:
>>
>>> Do we really need to force SysRq on or off? Maybe we should export
>>> __handle_sysrq() instead?
>>>
>> It seems cleanest to export __handle_sysrq() if that is ok?
>>
>
> Yes, I think this is the best option. Please feel free to merge through
> your tree.
>
Will do, I'll add your ack and queue it for the minor -rc1 fixes I am
accumulating for kgdb/kdb.
Thanks,
Jason.
next prev parent reply other threads:[~2010-05-24 20:50 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
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 [this message]
-- 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=4BFAE67C.6080000@windriver.com \
--to=jason.wessel@windriver$(echo .)com \
--cc=dmitry.torokhov@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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