linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux MM <linux-mm@kvack.org>,
	Thomas Garnier <thgarnie@google.com>
Subject: Re: linux-next: Tree for Jun 6 (mm/slub.c)
Date: Wed, 8 Jun 2016 09:31:57 +1000	[thread overview]
Message-ID: <20160608093157.51225c43@canb.auug.org.au> (raw)
In-Reply-To: <20160607131242.fac39cbade676df24d70edaa@linux-foundation.org>

Hi Andrew,

On Tue, 7 Jun 2016 13:12:42 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 6 Jun 2016 22:11:37 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> 
> > On 06/05/16 21:20, Stephen Rothwell wrote:  
> > > Hi all,
> > > 
> > > Changes since 20160603:
> > >   
> > 
> > on i386:
> > 
> > mm/built-in.o: In function `init_cache_random_seq':
> > slub.c:(.text+0x76921): undefined reference to `cache_random_seq_create'
> > mm/built-in.o: In function `__kmem_cache_release':
> > (.text+0x80525): undefined reference to `cache_random_seq_destroy'  
> 
> Yup.  This, I guess...
> 
> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: mm-slub-freelist-randomization-fix

Applied to linux-next today.

-- 
Cheers,
Stephen Rothwell

      parent reply	other threads:[~2016-06-07 23:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06  4:20 linux-next: Tree for Jun 6 Stephen Rothwell
2016-06-07  3:10 ` linux-next: Tree for Jun 6 (scsi_debug.c) Randy Dunlap
2016-08-23 23:22   ` Masanari Iida
2016-09-02 15:40     ` Randy Dunlap
2016-06-07  5:11 ` linux-next: Tree for Jun 6 (mm/slub.c) Randy Dunlap
2016-06-07 20:12   ` Andrew Morton
2016-06-07 21:37     ` Randy Dunlap
2016-06-07 23:31     ` Stephen Rothwell [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=20160608093157.51225c43@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=thgarnie@google.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;
as well as URLs for NNTP newsgroup(s).