All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: tglx@linutronix.de, mingo@redhat.com, catalin.marinas@arm.com,
	james.morse@arm.com, dyoung@redhat.com, bhsharma@redhat.com,
	horms@verge.net.au, guohanjun@huawei.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v6 0/4] support reserving crashkernel above 4G on arm64 kdump
Date: Wed, 18 Dec 2019 09:09:32 +0000	[thread overview]
Message-ID: <20191218090932.GA14061@willie-the-truck> (raw)
In-Reply-To: <2a97b296-59e7-0a26-84fa-e2ddcd7987b6@huawei.com>

On Wed, Dec 18, 2019 at 10:07:59AM +0800, Chen Zhou wrote:
> Friendly ping...

You broke the build:

https://lore.kernel.org/lkml/201909010744.CDe940pv%lkp@intel.com
https://lore.kernel.org/lkml/201909010704.4m9y2sg7%lkp@intel.com

So I doubt anybody will seriously look at this.

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: horms@verge.net.au, catalin.marinas@arm.com, bhsharma@redhat.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, james.morse@arm.com, guohanjun@huawei.com,
	tglx@linutronix.de, dyoung@redhat.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/4] support reserving crashkernel above 4G on arm64 kdump
Date: Wed, 18 Dec 2019 09:09:32 +0000	[thread overview]
Message-ID: <20191218090932.GA14061@willie-the-truck> (raw)
In-Reply-To: <2a97b296-59e7-0a26-84fa-e2ddcd7987b6@huawei.com>

On Wed, Dec 18, 2019 at 10:07:59AM +0800, Chen Zhou wrote:
> Friendly ping...

You broke the build:

https://lore.kernel.org/lkml/201909010744.CDe940pv%lkp@intel.com
https://lore.kernel.org/lkml/201909010704.4m9y2sg7%lkp@intel.com

So I doubt anybody will seriously look at this.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: horms@verge.net.au, catalin.marinas@arm.com, bhsharma@redhat.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, james.morse@arm.com, guohanjun@huawei.com,
	tglx@linutronix.de, dyoung@redhat.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/4] support reserving crashkernel above 4G on arm64 kdump
Date: Wed, 18 Dec 2019 09:09:32 +0000	[thread overview]
Message-ID: <20191218090932.GA14061@willie-the-truck> (raw)
In-Reply-To: <2a97b296-59e7-0a26-84fa-e2ddcd7987b6@huawei.com>

On Wed, Dec 18, 2019 at 10:07:59AM +0800, Chen Zhou wrote:
> Friendly ping...

You broke the build:

https://lore.kernel.org/lkml/201909010744.CDe940pv%lkp@intel.com
https://lore.kernel.org/lkml/201909010704.4m9y2sg7%lkp@intel.com

So I doubt anybody will seriously look at this.

Will

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

  reply	other threads:[~2019-12-18  9:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  7:11 [PATCH v6 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2019-08-30  7:11 ` Chen Zhou
2019-08-30  7:11 ` Chen Zhou
2019-08-30  7:11 ` [PATCH v6 1/4] x86: kdump: move reserve_crashkernel_low() into crash_core.c Chen Zhou
2019-08-30  7:11   ` Chen Zhou
2019-08-30  7:11   ` Chen Zhou
2019-08-31 23:12   ` kbuild test robot
2019-08-31 23:12     ` kbuild test robot
2019-08-31 23:12     ` kbuild test robot
2019-08-31 23:48   ` kbuild test robot
2019-08-31 23:48     ` kbuild test robot
2019-08-31 23:48     ` kbuild test robot
2019-08-30  7:11 ` [PATCH v6 2/4] arm64: kdump: reserve crashkenel above 4G for crash dump kernel Chen Zhou
2019-08-30  7:11   ` Chen Zhou
2019-08-30  7:11   ` Chen Zhou
2019-08-30  7:11 ` [PATCH v6 3/4] arm64: kdump: add memory for devices by DT property, low-memory-range Chen Zhou
2019-08-30  7:11   ` Chen Zhou
2019-08-30  7:11   ` Chen Zhou
2019-08-30  7:12 ` [PATCH v6 4/4] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2019-08-30  7:12   ` Chen Zhou
2019-08-30  7:12   ` Chen Zhou
2019-12-18  2:07 ` [PATCH v6 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2019-12-18  2:07   ` Chen Zhou
2019-12-18  2:07   ` Chen Zhou
2019-12-18  9:09   ` Will Deacon [this message]
2019-12-18  9:09     ` Will Deacon
2019-12-18  9:09     ` Will Deacon
2019-12-19  1:35     ` Chen Zhou
2019-12-19  1:35       ` Chen Zhou
2019-12-19  1:35       ` Chen Zhou
2019-12-18 16:21   ` John Donnelly
2019-12-18 17:18   ` John Donnelly
2019-12-18 17:18     ` John Donnelly
2019-12-18 17:18     ` John Donnelly
2019-12-19  2:56     ` Chen Zhou
2019-12-19  2:56       ` Chen Zhou
2019-12-19  2:56       ` Chen Zhou
2019-12-19 18:33       ` ` John Donnelly
2019-12-20  1:44         ` ` Chen Zhou
2019-12-20  1:44           ` ` Chen Zhou

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=20191218090932.GA14061@willie-the-truck \
    --to=will@kernel.org \
    --cc=bhsharma@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=chenzhou10@huawei.com \
    --cc=dyoung@redhat.com \
    --cc=guohanjun@huawei.com \
    --cc=horms@verge.net.au \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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.