From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: michael@ellerman.id.au
Cc: Vivek Goyal <vgoyal@redhat.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/kdump: Fix /dev/oldmem interface
Date: Thu, 31 Jul 2008 14:50:20 +0530 [thread overview]
Message-ID: <489183D4.5060605@in.ibm.com> (raw)
In-Reply-To: <1217488357.1487.51.camel@localhost>
Michael Ellerman wrote:
> Heh, do I get a prize for being neurotic? ;) .. Or just stupid, ahem.
>
> I think you should also sign off on it Sachin, see clause (c) of the
> developers cert (http://lwn.net/Articles/139918/)
>
>
Here is a signed-off from me. Let me know if i need to resubmit
the patch with all signed-off-by lines.
Signed-off-by : Sachin Sant <sachinp@in.ibm.com>
--
Thanks
-Sachin
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
prev parent reply other threads:[~2008-07-31 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 6:54 [PATCH] powerpc/kdump: Fix /dev/oldmem interface Sachin P. Sant
2008-07-31 7:12 ` Michael Ellerman
2008-07-31 9:20 ` Sachin P. Sant [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=489183D4.5060605@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).