From: Will Deacon <will.deacon@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: mark.rutland@arm.com, geoff@infradead.org,
kexec@lists.infradead.org,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
james.morse@arm.com, bauerman@linux.vnet.ibm.com,
dyoung@redhat.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v28 0/9] arm64: add kdump support
Date: Tue, 29 Nov 2016 11:05:02 +0000 [thread overview]
Message-ID: <20161129110502.GE30283@arm.com> (raw)
In-Reply-To: <20161125162039.GB22099@e104818-lin.cambridge.arm.com>
On Fri, Nov 25, 2016 at 04:20:40PM +0000, Catalin Marinas wrote:
> On Thu, Nov 24, 2016 at 06:55:23PM +0900, AKASHI Takahiro wrote:
> > AKASHI Takahiro (8):
> > arm64: kdump: reserve memory for crash dump kernel
> > memblock: add memblock_cap_memory_range()
> > arm64: limit memory regions based on DT property, usable-memory-range
> > arm64: kdump: implement machine_crash_shutdown()
> > arm64: kdump: add kdump support
> > arm64: kdump: add VMCOREINFO's for user-space coredump tools
> > arm64: kdump: enable kdump in the arm64 defconfig
> > arm64: kdump: update a kernel doc
>
> Given that it's nearly -rc7, holiday in the US and more acks needed, we
> should defer merging this series to 4.11. In the meantime, since Will is
> going to handle the 4.11 merging window, I'm acking the whole series:
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Okey doke. I'll keep my eyes peeled for a new version in the new year.
Will
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v28 0/9] arm64: add kdump support
Date: Tue, 29 Nov 2016 11:05:02 +0000 [thread overview]
Message-ID: <20161129110502.GE30283@arm.com> (raw)
In-Reply-To: <20161125162039.GB22099@e104818-lin.cambridge.arm.com>
On Fri, Nov 25, 2016 at 04:20:40PM +0000, Catalin Marinas wrote:
> On Thu, Nov 24, 2016 at 06:55:23PM +0900, AKASHI Takahiro wrote:
> > AKASHI Takahiro (8):
> > arm64: kdump: reserve memory for crash dump kernel
> > memblock: add memblock_cap_memory_range()
> > arm64: limit memory regions based on DT property, usable-memory-range
> > arm64: kdump: implement machine_crash_shutdown()
> > arm64: kdump: add kdump support
> > arm64: kdump: add VMCOREINFO's for user-space coredump tools
> > arm64: kdump: enable kdump in the arm64 defconfig
> > arm64: kdump: update a kernel doc
>
> Given that it's nearly -rc7, holiday in the US and more acks needed, we
> should defer merging this series to 4.11. In the meantime, since Will is
> going to handle the 4.11 merging window, I'm acking the whole series:
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Okey doke. I'll keep my eyes peeled for a new version in the new year.
Will
next prev parent reply other threads:[~2016-11-29 11:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 9:55 [PATCH v28 0/9] arm64: add kdump support AKASHI Takahiro
2016-11-24 9:55 ` AKASHI Takahiro
2016-11-24 9:57 ` [PATCH v28 1/9] memblock: add memblock_cap_memory_range() AKASHI Takahiro
2016-11-24 9:57 ` AKASHI Takahiro
2016-11-24 9:57 ` AKASHI Takahiro
2016-11-24 10:26 ` Catalin Marinas
2016-11-24 10:26 ` Catalin Marinas
2016-11-24 10:26 ` Catalin Marinas
2016-11-24 9:58 ` [PATCH v28 2/9] arm64: limit memory regions based on DT property, usable-memory-range AKASHI Takahiro
2016-11-24 9:58 ` AKASHI Takahiro
2016-11-24 9:58 ` [PATCH v28 3/9] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-11-24 9:58 ` AKASHI Takahiro
2016-11-24 9:58 ` [PATCH v28 4/9] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-11-24 9:58 ` AKASHI Takahiro
2016-11-28 15:04 ` Catalin Marinas
2016-11-28 15:04 ` Catalin Marinas
2016-11-29 5:47 ` AKASHI Takahiro
2016-11-29 5:47 ` AKASHI Takahiro
2016-11-24 9:58 ` [PATCH v28 5/9] arm64: kdump: add VMCOREINFO's for user-space tools AKASHI Takahiro
2016-11-24 9:58 ` AKASHI Takahiro
2016-11-24 9:58 ` [PATCH v28 6/9] arm64: kdump: provide /proc/vmcore file AKASHI Takahiro
2016-11-24 9:58 ` AKASHI Takahiro
2016-11-24 9:58 ` [PATCH v28 7/9] arm64: kdump: enable kdump in defconfig AKASHI Takahiro
2016-11-24 9:58 ` AKASHI Takahiro
2016-11-24 9:58 ` [PATCH v28 8/9] Documentation: kdump: describe arm64 port AKASHI Takahiro
2016-11-24 9:58 ` AKASHI Takahiro
2016-11-24 9:59 ` [PATCH v28 9/9] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro
2016-11-24 9:59 ` AKASHI Takahiro
2016-11-24 9:59 ` AKASHI Takahiro
2016-11-24 17:14 ` Catalin Marinas
2016-11-24 17:14 ` Catalin Marinas
2016-11-24 17:14 ` Catalin Marinas
2016-11-30 20:44 ` Rob Herring
2016-11-30 20:44 ` Rob Herring
2016-11-30 20:44 ` Rob Herring
2016-11-25 16:20 ` [PATCH v28 0/9] arm64: add kdump support Catalin Marinas
2016-11-25 16:20 ` Catalin Marinas
2016-11-29 11:05 ` Will Deacon [this message]
2016-11-29 11:05 ` Will Deacon
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=20161129110502.GE30283@arm.com \
--to=will.deacon@arm.com \
--cc=bauerman@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=dyoung@redhat.com \
--cc=geoff@infradead.org \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=takahiro.akashi@linaro.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 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.