linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>,
	Rob Herring <robherring2@gmail.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: Re: linux-next: Tree for Oct 15
Date: Mon, 15 Oct 2018 15:13:19 -0700	[thread overview]
Message-ID: <20181015151319.3a443f0421c20bd7ed055cb9@linux-foundation.org> (raw)
In-Reply-To: <20181016072439.42613abd@canb.auug.org.au>

On Tue, 16 Oct 2018 07:24:39 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> On Tue, 16 Oct 2018 07:12:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Mon, 15 Oct 2018 11:26:37 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
> > >
> > > ALl ppc qemu tests (including big endian pseries) also generate a warning.
> > > 
> > > WARNING: CPU: 0 PID: 0 at mm/memblock.c:1301 .memblock_alloc_range_nid+0x20/0x68
> 
> That is:
> 
> static phys_addr_t __init memblock_alloc_range_nid(phys_addr_t size,
>                                         phys_addr_t align, phys_addr_t start,
>                                         phys_addr_t end, int nid,
>                                         enum memblock_flags flags)
> {
>        if (WARN_ON_ONCE(!align))
>                 align = SMP_CACHE_BYTES;
> 
> Looks like patch
> 
>   "memblock: stop using implicit alignment to SMP_CACHE_BYTES"
> 
> missed some places ...

To be expected, I guess.  I'm pretty relaxed about this ;) Let's do
another sweep in a week or so, after which we'll have a couple of
months to mop up any leftovers.

  reply	other threads:[~2018-10-15 22:13 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  8:25 linux-next: Tree for Oct 15 Stephen Rothwell
2018-10-15 18:26 ` Guenter Roeck
2018-10-15 20:12   ` Stephen Rothwell
2018-10-15 20:24     ` Stephen Rothwell
2018-10-15 22:13       ` Andrew Morton [this message]
2018-10-16 13:36         ` Mike Rapoport
2018-10-16 20:41           ` Stephen Rothwell
2018-10-15 20:35     ` Rob Herring
2018-10-15 21:18       ` Guenter Roeck
2018-10-15 21:48         ` Rob Herring
2018-10-15 22:10           ` Guenter Roeck
2018-10-15 22:13             ` Rob Herring
2018-10-15 22:28               ` Guenter Roeck
2018-10-15 22:34               ` Guenter Roeck
2018-10-15 22:52                 ` Rob Herring
2018-10-16  1:00       ` Rob Herring
2018-10-16  1:34         ` David Miller
2018-10-15 19:39 ` Guenter Roeck
2018-10-15 20:33   ` Stephen Rothwell
2018-10-15 21:35     ` Guenter Roeck
2018-10-15 22:22     ` Guenter Roeck
2018-10-16  2:02       ` Stephen Rothwell
2018-10-16  2:19         ` Stephen Rothwell
2018-10-16  3:12           ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2021-10-15 10:06 Stephen Rothwell
2020-10-15  7:28 Stephen Rothwell
2019-10-15  5:16 Stephen Rothwell
2015-10-15  7:51 Stephen Rothwell
2014-10-15  4:29 Stephen Rothwell
2013-10-15 14:02 Thierry Reding
2013-10-16  5:21 ` Guenter Roeck
2013-10-16 15:50   ` Thierry Reding
2013-10-16 16:37     ` Guenter Roeck
2013-10-16 16:43       ` Thierry Reding
2012-10-15  2:41 Stephen Rothwell
2008-10-15 10:58 linux-next tree " Stephen Rothwell

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=20181015151319.3a443f0421c20bd7ed055cb9@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=robherring2@gmail.com \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=sfr@canb.auug.org.au \
    /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).