linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lauraa@codeaurora.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: mm: dump: a couple of fixes
Date: Wed, 10 Dec 2014 09:56:13 -0800	[thread overview]
Message-ID: <5488893D.9080307@codeaurora.org> (raw)
In-Reply-To: <1417782895-13657-1-git-send-email-mark.rutland@arm.com>

On 12/5/2014 4:34 AM, Mark Rutland wrote:
> While using the mm dump code, I spotted a couple of issues; one build warning
> and one theoretical failure on systems endowed with plenty of RAM (as with ARM
> [1], though arm64 requires a slightly different resolution). These patches
> (based on next-20141205), fix those issues.
>
> Mark.
>
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/308952.html
>
> Mark Rutland (2):
>    arm64: mm: dump: fix shift warning
>    arm64: mm: dump: don't skip final region
>
>   arch/arm64/mm/dump.c | 5 +----
>   1 file changed, 1 insertion(+), 4 deletions(-)
>

If they haven't been picked up yet:

Acked-by: Laura Abbott <lauraa@codeaurora.org>

-- 
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  parent reply	other threads:[~2014-12-10 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 12:34 [PATCH 0/2] arm64: mm: dump: a couple of fixes Mark Rutland
2014-12-05 12:34 ` [PATCH 1/2] arm64: mm: dump: fix shift warning Mark Rutland
2014-12-05 13:39   ` Steve Capper
2014-12-05 13:42     ` Mark Rutland
2014-12-05 12:34 ` [PATCH 2/2] arm64: mm: dump: don't skip final region Mark Rutland
2014-12-05 16:08   ` Steve Capper
2014-12-10 17:56 ` Laura Abbott [this message]
2014-12-11 18:20   ` [PATCH 0/2] arm64: mm: dump: a couple of fixes Mark Rutland

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=5488893D.9080307@codeaurora.org \
    --to=lauraa@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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 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).