From: Tyler Baker <tyler.baker@linaro.org>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>,
Tang Chen <tangchen@cn.fujitsu.com>,
Pekka Enberg <penberg@kernel.org>,
Wei Yang <weiyang@linux.vnet.ibm.com>,
Linux MM <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kevin's boot bot <khilman@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] mm/memblock: use memblock_insert_region() for the empty array
Date: Wed, 9 Dec 2015 10:59:40 -0800 [thread overview]
Message-ID: <CANMBJr7U3DfsRC4ATx0=d6pVFXGJJAB2qs2sRS1dZ3xV5csZzg@mail.gmail.com> (raw)
In-Reply-To: <1449300220-30108-1-git-send-email-kuleshovmail@gmail.com>
On 4 December 2015 at 23:23, Alexander Kuleshov <kuleshovmail@gmail.com> wrote:
> We have the special case for an empty array in the memblock_add_range()
> function. In the same time we have almost the same functional in the
> memblock_insert_region() function. Let's use the memblock_insert_region()
> instead of direct initialization.
>
> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
Just to add on to the report from Dan, the kernelci.org boot bot has
also detected ~65 new boot failures in next-20151209[1], which have
been bisected to this patch[2]. It doesn't revert cleanly, so I'm
going to try to clean it up by hand and see if it resolves the issue.
Cheers,
Tyler
[1] http://kernelci.org/boot/all/job/next/kernel/next-20151209/
[2] http://hastebin.com/ufiwonuraw.vhdl
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-12-09 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 7:23 Alexander Kuleshov
2015-12-09 18:46 ` Dan Williams
2015-12-09 18:59 ` Tyler Baker [this message]
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='CANMBJr7U3DfsRC4ATx0=d6pVFXGJJAB2qs2sRS1dZ3xV5csZzg@mail.gmail.com' \
--to=tyler.baker@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=khilman@kernel.org \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=tangchen@cn.fujitsu.com \
--cc=tony.luck@intel.com \
--cc=weiyang@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox