From: Maxim Uvarov <muvarov@gmail.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org, kexec@lists.infradead.org,
horms@verge.net.au, ralf@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS kexec,kdump support
Date: Thu, 4 Mar 2010 14:35:37 +0300 [thread overview]
Message-ID: <572af9171003040335w16434350y60a9f39676dbfa3d@mail.gmail.com> (raw)
In-Reply-To: <4B8E9E0C.4050809@caviumnetworks.com>
2010/3/3 David Daney <ddaney@caviumnetworks.com>:
> On 03/03/2010 03:05 AM, Maxim Uvarov wrote:
>>
>> Hello folks,
>>
>> Please find here MIPS crash and kdump patches.
>> This is patch set of 3 patches:
>> 1. generic MIPS changes (kernel);
>> 2. MIPS Cavium Octeon board kexec/kdump code (kernel);
>> 3. Kexec user space MIPS changes.
>>
>> Patches were tested on the latest linux-mips@ git kernel and the latest
>> kexec-tools git on Cavium Octeon 50xx board.
>>
>> I also made the same code working on RMI XLR/XLS boards for both
>> mips32 and mips64 kernels.
>>
>> Best regards,
>> Maxim Uvarov.
>>
>>
>> ---
>>
>> arch/mips/Kconfig | 24 ++++++++++
>
> [...]
>>
>>
>> Signed-off-by: Maxim Uvarov<muvarov@gmail.com>
>>
>
> That Signed-off-by: needs to be just above the '---' not at the end.
>
> David Daney
>
Thanks David, I corrected stgit email template. I think I don't need
resend patches with only this change.
--
Best regards,
Maxim Uvarov
prev parent reply other threads:[~2010-03-04 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 11:05 [PATCH 1/2] MIPS kexec,kdump support Maxim Uvarov
2010-03-03 11:05 ` [PATCH 2/2] MIPS Cavium Octeon board " Maxim Uvarov
2010-03-03 16:34 ` [PATCH 1/2] MIPS " wilbur.chan
2010-03-04 11:58 ` Maxim Uvarov
2010-03-03 17:36 ` David Daney
2010-03-04 11:35 ` Maxim Uvarov [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=572af9171003040335w16434350y60a9f39676dbfa3d@mail.gmail.com \
--to=muvarov@gmail.com \
--cc=ddaney@caviumnetworks.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox