All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	Dave Young <dyoung@redhat.com>,
	kexec-ml <kexec@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org,
	"vgoyal@redhat.com" <vgoyal@redhat.com>
Subject: Re: [PATCH v4 2/5] ia64: reuse append_elf_note() and final_note() functions
Date: Thu, 26 Jan 2017 00:45:52 +0530	[thread overview]
Message-ID: <04b96f50-f77d-9446-975f-7d44accfe583@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+8MBb+g604VGLLibB+eOAtF_h1r5mYJRdjaGE8UgWQ+JPGDdg@mail.gmail.com>



On Tuesday 24 January 2017 11:53 PM, Tony Luck wrote:
> On Tue, Jan 24, 2017 at 10:11 AM, Hari Bathini
> <hbathini@linux.vnet.ibm.com> wrote:
>
>> Hello IA64 folks,
>>
>> Could you please review this patch..?
> It looks OK in principal.  My lab is in partial disarray at the
> moment (just got back from a sabbatical) so I can't test
> build and boot. Have you cross-compiled it (or gotten a success
> build report from zero-day)?

I haven't gotten a success/failure build report from zero-day. Not sure 
what to make of it.
But I did try cross-compiling and it was successful. Should that do?

Thanks
Hari


> If you have ... then add an Acked-by: Tony Luck <tony.luck@intel.com>
>
> -Tony
>

WARNING: multiple messages have this Message-ID (diff)
From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org,
	kexec-ml <kexec@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Dave Young <dyoung@redhat.com>,
	"vgoyal@redhat.com" <vgoyal@redhat.com>
Subject: Re: [PATCH v4 2/5] ia64: reuse append_elf_note() and final_note() functions
Date: Thu, 26 Jan 2017 00:45:52 +0530	[thread overview]
Message-ID: <04b96f50-f77d-9446-975f-7d44accfe583@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+8MBb+g604VGLLibB+eOAtF_h1r5mYJRdjaGE8UgWQ+JPGDdg@mail.gmail.com>



On Tuesday 24 January 2017 11:53 PM, Tony Luck wrote:
> On Tue, Jan 24, 2017 at 10:11 AM, Hari Bathini
> <hbathini@linux.vnet.ibm.com> wrote:
>
>> Hello IA64 folks,
>>
>> Could you please review this patch..?
> It looks OK in principal.  My lab is in partial disarray at the
> moment (just got back from a sabbatical) so I can't test
> build and boot. Have you cross-compiled it (or gotten a success
> build report from zero-day)?

I haven't gotten a success/failure build report from zero-day. Not sure 
what to make of it.
But I did try cross-compiling and it was successful. Should that do?

Thanks
Hari


> If you have ... then add an Acked-by: Tony Luck <tony.luck@intel.com>
>
> -Tony
>


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	Dave Young <dyoung@redhat.com>,
	kexec-ml <kexec@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org,
	"vgoyal@redhat.com" <vgoyal@redhat.com>
Subject: Re: [PATCH v4 2/5] ia64: reuse append_elf_note() and final_note() functions
Date: Wed, 25 Jan 2017 19:27:52 +0000	[thread overview]
Message-ID: <04b96f50-f77d-9446-975f-7d44accfe583@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+8MBb+g604VGLLibB+eOAtF_h1r5mYJRdjaGE8UgWQ+JPGDdg@mail.gmail.com>



On Tuesday 24 January 2017 11:53 PM, Tony Luck wrote:
> On Tue, Jan 24, 2017 at 10:11 AM, Hari Bathini
> <hbathini@linux.vnet.ibm.com> wrote:
>
>> Hello IA64 folks,
>>
>> Could you please review this patch..?
> It looks OK in principal.  My lab is in partial disarray at the
> moment (just got back from a sabbatical) so I can't test
> build and boot. Have you cross-compiled it (or gotten a success
> build report from zero-day)?

I haven't gotten a success/failure build report from zero-day. Not sure 
what to make of it.
But I did try cross-compiling and it was successful. Should that do?

Thanks
Hari


> If you have ... then add an Acked-by: Tony Luck <tony.luck@intel.com>
>
> -Tony
>


  reply	other threads:[~2017-01-25 19:16 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 17:28 [PATCH v4 0/5] kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel parameter for fadump Hari Bathini
2017-01-05 17:40 ` [PATCH v4 0/5] kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel parameter for Hari Bathini
2017-01-05 17:28 ` [PATCH v4 0/5] kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel parameter for fadump Hari Bathini
2017-01-05 17:29 ` [PATCH v4 1/5] crash: move crashkernel parsing and vmcore related code under CONFIG_CRASH_CORE Hari Bathini
2017-01-05 17:41   ` Hari Bathini
2017-01-05 17:29   ` Hari Bathini
2017-01-06  2:02   ` Dave Young
2017-01-06  2:02     ` Dave Young
2017-01-06  2:02     ` Dave Young
2017-03-23 15:54   ` Hari Bathini
2017-03-23 15:55     ` Hari Bathini
2017-03-23 15:54     ` Hari Bathini
2017-01-05 17:31 ` [PATCH v4 2/5] ia64: reuse append_elf_note() and final_note() functions Hari Bathini
2017-01-05 17:43   ` Hari Bathini
2017-01-05 17:31   ` Hari Bathini
2017-01-06  2:03   ` Dave Young
2017-01-06  2:03     ` Dave Young
2017-01-06  2:03     ` Dave Young
2017-01-17 17:06     ` Hari Bathini
2017-01-17 17:18       ` Hari Bathini
2017-01-17 17:06       ` Hari Bathini
2017-01-24 18:11       ` Hari Bathini
2017-01-24 18:23         ` Hari Bathini
2017-01-24 18:11         ` Hari Bathini
2017-01-24 18:23         ` Tony Luck
2017-01-24 18:23           ` Tony Luck
2017-01-24 18:23           ` Tony Luck
2017-01-25 19:15           ` Hari Bathini [this message]
2017-01-25 19:27             ` Hari Bathini
2017-01-25 19:15             ` Hari Bathini
2017-01-31 22:21             ` Tony Luck
2017-01-31 22:21               ` Tony Luck
2017-01-31 22:21               ` Tony Luck
2017-02-01  1:11               ` Michael Ellerman
2017-02-01  1:11                 ` Michael Ellerman
2017-02-01  1:11                 ` Michael Ellerman
2017-01-20  5:47   ` Michael Ellerman
2017-01-20  5:47     ` Michael Ellerman
2017-01-20  5:47     ` Michael Ellerman
2017-01-24 18:08     ` Hari Bathini
2017-01-24 18:20       ` Hari Bathini
2017-01-24 18:08       ` Hari Bathini
2017-01-05 17:32 ` [PATCH v4 3/5] powerpc/fadump: remove dependency with CONFIG_KEXEC Hari Bathini
2017-01-05 17:44   ` Hari Bathini
2017-01-05 17:32   ` Hari Bathini
2017-01-13 11:27   ` Mahesh Jagannath Salgaonkar
2017-01-13 11:39     ` Mahesh Jagannath Salgaonkar
2017-01-13 11:27     ` Mahesh Jagannath Salgaonkar
2017-01-05 17:32 ` [PATCH v4 4/5] powerpc/fadump: reuse crashkernel parameter for fadump memory reservation Hari Bathini
2017-01-05 17:44   ` Hari Bathini
2017-01-05 17:32   ` Hari Bathini
2017-01-13 11:51   ` Mahesh Jagannath Salgaonkar
2017-01-13 11:51     ` Mahesh Jagannath Salgaonkar
2017-01-13 11:51     ` Mahesh Jagannath Salgaonkar
2017-01-05 17:32 ` [PATCH v4 5/5] powerpc/fadump: update documentation about crashkernel parameter reuse Hari Bathini
2017-01-05 17:44   ` Hari Bathini
2017-01-05 17:32   ` Hari Bathini

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=04b96f50-f77d-9446-975f-7d44accfe583@linux.vnet.ibm.com \
    --to=hbathini@linux.vnet.ibm.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=fenghua.yu@intel.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=tony.luck@gmail.com \
    --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 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.