From: lijiang <lijiang@redhat.com> To: Borislav Petkov <bp@alien8.de> Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, bhe@redhat.com, dyoung@redhat.com, jgross@suse.com, dhowells@redhat.com, Thomas.Lendacky@amd.com, ebiederm@xmission.com, vgoyal@redhat.com, kexec@lists.infradead.org Subject: Re: [PATCH 1/3 v4] x86/kdump: always reserve the low 1MiB when the crashkernel option is specified Date: Wed, 23 Oct 2019 17:20:50 +0800 [thread overview] Message-ID: <98c9f97d-de22-2041-d0a4-214542807706@redhat.com> (raw) In-Reply-To: <20191023074602.GB16060@zn.tnic> 在 2019年10月23日 15:46, Borislav Petkov 写道: > On Wed, Oct 23, 2019 at 01:35:09PM +0800, lijiang wrote: >> Would you mind if i improve this patch as follow? Thanks. > > Yap, looks good to me. > Thanks for your comment. OK. I will post this one and the third patch in this series later. Thanks. Lianbo > Thx. >
WARNING: multiple messages have this Message-ID (diff)
From: lijiang <lijiang@redhat.com> To: Borislav Petkov <bp@alien8.de> Cc: jgross@suse.com, Thomas.Lendacky@amd.com, bhe@redhat.com, x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, dhowells@redhat.com, mingo@redhat.com, ebiederm@xmission.com, hpa@zytor.com, tglx@linutronix.de, dyoung@redhat.com, vgoyal@redhat.com Subject: Re: [PATCH 1/3 v4] x86/kdump: always reserve the low 1MiB when the crashkernel option is specified Date: Wed, 23 Oct 2019 17:20:50 +0800 [thread overview] Message-ID: <98c9f97d-de22-2041-d0a4-214542807706@redhat.com> (raw) In-Reply-To: <20191023074602.GB16060@zn.tnic> 在 2019年10月23日 15:46, Borislav Petkov 写道: > On Wed, Oct 23, 2019 at 01:35:09PM +0800, lijiang wrote: >> Would you mind if i improve this patch as follow? Thanks. > > Yap, looks good to me. > Thanks for your comment. OK. I will post this one and the third patch in this series later. Thanks. Lianbo > Thx. > _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-10-23 9:21 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-17 9:43 [PATCH 0/3 v4] x86/kdump: Fix 'kmem -s' reported an invalid freepointer when SME was active Lianbo Jiang 2019-10-17 9:43 ` Lianbo Jiang 2019-10-17 9:43 ` [PATCH 1/3 v4] x86/kdump: always reserve the low 1MiB when the crashkernel option is specified Lianbo Jiang 2019-10-17 9:43 ` Lianbo Jiang 2019-10-22 8:30 ` Borislav Petkov 2019-10-22 8:30 ` Borislav Petkov 2019-10-23 5:23 ` lijiang 2019-10-23 5:23 ` lijiang 2019-10-23 7:43 ` Borislav Petkov 2019-10-23 7:43 ` Borislav Petkov 2019-10-23 5:35 ` lijiang 2019-10-23 5:35 ` lijiang 2019-10-23 7:46 ` Borislav Petkov 2019-10-23 7:46 ` Borislav Petkov 2019-10-23 9:20 ` lijiang [this message] 2019-10-23 9:20 ` lijiang 2019-10-24 8:13 ` d.hatayama 2019-10-24 8:13 ` d.hatayama 2019-10-24 9:10 ` Borislav Petkov 2019-10-24 9:10 ` Borislav Petkov 2019-10-24 11:24 ` lijiang 2019-10-24 11:24 ` lijiang 2019-10-24 22:12 ` [PATCH] x86/kdump: always reserve the low 1MiB when the crashkernel kbuild test robot 2019-10-24 22:12 ` kbuild test robot 2019-10-24 22:12 ` kbuild test robot 2019-10-24 23:55 ` lijiang 2019-10-24 23:55 ` lijiang 2019-10-24 23:55 ` lijiang 2019-10-17 9:43 ` [PATCH 2/3 v4] x86/kdump: remove the unused crash_copy_backup_region() Lianbo Jiang 2019-10-17 9:43 ` Lianbo Jiang 2019-10-17 9:43 ` [PATCH 3/3 v4] x86/kdump: clean up all the code related to the backup region Lianbo Jiang 2019-10-17 9:43 ` Lianbo Jiang 2019-10-22 12:15 ` Borislav Petkov 2019-10-22 12:15 ` Borislav Petkov [not found] <mailman.5359.1571746554.2486.kexec@lists.infradead.org> 2019-10-22 13:38 ` [PATCH 1/3 v4] x86/kdump: always reserve the low 1MiB when the crashkernel option is specified Dave Anderson [not found] <55902207.7797907.1571751831873.JavaMail.zimbra@redhat.com> 2019-10-22 13:43 ` Dave 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=98c9f97d-de22-2041-d0a4-214542807706@redhat.com \ --to=lijiang@redhat.com \ --cc=Thomas.Lendacky@amd.com \ --cc=bhe@redhat.com \ --cc=bp@alien8.de \ --cc=dhowells@redhat.com \ --cc=dyoung@redhat.com \ --cc=ebiederm@xmission.com \ --cc=hpa@zytor.com \ --cc=jgross@suse.com \ --cc=kexec@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@redhat.com \ --cc=tglx@linutronix.de \ --cc=vgoyal@redhat.com \ --cc=x86@kernel.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: linkBe 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.