All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Roman Gushchin <guro@fb.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Michal Hocko <mhocko@suse.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Build fails with SLOB in next
Date: Thu, 8 Mar 2018 09:28:49 -0800	[thread overview]
Message-ID: <20180308172849.GO5799@atomide.com> (raw)

Hi,

Looks like commit 8b1747684ff8 ("dcache: account external names as
indirectly reclaimable memory") caused build fail if SLOB is selected:

fs/dcache.c: In function '__d_free_external':
fs/dcache.c:278:22: error: implicit declaration of function
'kmalloc_index'; did you mean 'kmalloc_ node'?
[-Werror=implicit-function-declaration]
        -kmalloc_size(kmalloc_index(bytes)));
	                      ^~~~~~~~~~~~~

Is this already fixed somewhere?

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Build fails with SLOB in next
Date: Thu, 8 Mar 2018 09:28:49 -0800	[thread overview]
Message-ID: <20180308172849.GO5799@atomide.com> (raw)

Hi,

Looks like commit 8b1747684ff8 ("dcache: account external names as
indirectly reclaimable memory") caused build fail if SLOB is selected:

fs/dcache.c: In function '__d_free_external':
fs/dcache.c:278:22: error: implicit declaration of function
'kmalloc_index'; did you mean 'kmalloc_ node'?
[-Werror=implicit-function-declaration]
        -kmalloc_size(kmalloc_index(bytes)));
	                      ^~~~~~~~~~~~~

Is this already fixed somewhere?

Regards,

Tony

             reply	other threads:[~2018-03-08 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 17:28 Tony Lindgren [this message]
2018-03-08 17:28 ` Build fails with SLOB in next Tony Lindgren
2018-03-08 22:11 ` Roman Gushchin
2018-03-08 22:11   ` Roman Gushchin
2018-03-08 22:11   ` Roman Gushchin

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=20180308172849.GO5799@atomide.com \
    --to=tony@atomide.com \
    --cc=akpm@linux-foundation.org \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    /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.