From: Mohan Kumar M <mohan@in.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, kexec@lists.infradead.org
Subject: Re: [PATCH] Support for relocatable kdump kernel
Date: Thu, 16 Oct 2008 16:03:12 +0530 [thread overview]
Message-ID: <48F71868.8000507@in.ibm.com> (raw)
In-Reply-To: <18674.42140.69339.584403@drongo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Mohan Kumar M writes:
>
>> Support for relocatable kdump kernel
>
>> @@ -1401,9 +1414,21 @@ _STATIC(__after_prom_start)
>> beq 9f /* have already put us at zero */
>> li r6,0x100 /* Start offset, the first 0x100 */
>> /* bytes were copied earlier. */
>> -#ifdef CONFIG_RELOCATABLE
>> +
>> +#ifdef CONFIG_CRASH_DUMP
>
> What tree is this patch against? No tree that I can find has a line
> saying "#ifdef CONFIG_RELOCATABLE" at that point. Or is there a
> prerequisite patch that I haven't seen yet?
Hi Paul,
My patch is based on your PATCH 5 of relocatable kernel patchset (which
demonstrates kernel can be relocatable).
Do I need to resend the patch by generating the diff with your patch5 also?
Regards,
Mohan.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Mohan Kumar M <mohan@in.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, kexec@lists.infradead.org
Subject: Re: [PATCH] Support for relocatable kdump kernel
Date: Thu, 16 Oct 2008 16:03:12 +0530 [thread overview]
Message-ID: <48F71868.8000507@in.ibm.com> (raw)
In-Reply-To: <18674.42140.69339.584403@drongo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Mohan Kumar M writes:
>
>> Support for relocatable kdump kernel
>
>> @@ -1401,9 +1414,21 @@ _STATIC(__after_prom_start)
>> beq 9f /* have already put us at zero */
>> li r6,0x100 /* Start offset, the first 0x100 */
>> /* bytes were copied earlier. */
>> -#ifdef CONFIG_RELOCATABLE
>> +
>> +#ifdef CONFIG_CRASH_DUMP
>
> What tree is this patch against? No tree that I can find has a line
> saying "#ifdef CONFIG_RELOCATABLE" at that point. Or is there a
> prerequisite patch that I haven't seen yet?
Hi Paul,
My patch is based on your PATCH 5 of relocatable kernel patchset (which
demonstrates kernel can be relocatable).
Do I need to resend the patch by generating the diff with your patch5 also?
Regards,
Mohan.
next prev parent reply other threads:[~2008-10-16 10:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 23:34 [PATCH] Support for relocatable kdump kernel Mohan Kumar M
2008-10-12 23:34 ` Mohan Kumar M
2008-10-13 1:30 ` Paul Mackerras
2008-10-13 1:30 ` Paul Mackerras
2008-10-16 10:33 ` Mohan Kumar M [this message]
2008-10-16 10:33 ` Mohan Kumar M
-- strict thread matches above, loose matches on Subject: below --
2008-10-22 4:56 Milton Miller
2008-10-22 3:38 Michael Ellerman
[not found] <18684.5062.154465.668614@drongo.ozlabs.ibm.com>
2008-10-20 6:43 ` Michael Ellerman
2008-10-20 6:43 ` Michael Ellerman
2008-10-20 9:34 ` Mohan Kumar M
2008-10-20 9:34 ` Mohan Kumar M
2008-10-21 6:03 ` Michael Ellerman
2008-10-21 6:03 ` Michael Ellerman
2008-10-21 18:21 ` Mohan Kumar M
2008-10-21 18:21 ` Mohan Kumar M
2008-10-01 18:26 Mohan Kumar M
2008-10-01 18:26 ` Mohan Kumar M
2008-10-09 5:27 ` Paul Mackerras
2008-10-09 5:27 ` Paul Mackerras
2008-10-09 16:35 ` Mohan Kumar M
2008-10-09 16:35 ` Mohan Kumar M
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=48F71868.8000507@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.