linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Joern Engel <joern@logfs.org>
Subject: Re: linux-next: Tree for Dec 21 (logfs)
Date: Mon, 21 Dec 2015 09:37:18 -0800	[thread overview]
Message-ID: <567838CE.1050301@infradead.org> (raw)
In-Reply-To: <20151221190526.48a9ad86@canb.auug.org.au>

On 12/21/15 00:05, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20151218:
> 

on i386 or x86_64:

when CONFIG_MTD=m and CONFIG_LOGFS=y:

fs/built-in.o: In function `logfs_mount':
super.c:(.text+0xb695e): undefined reference to `logfs_get_sb_mtd'
fs/built-in.o: In function `logfs_get_sb_bdev':
(.text+0xb764a): undefined reference to `logfs_get_sb_mtd'


-- 
~Randy

      reply	other threads:[~2015-12-21 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21  8:05 linux-next: Tree for Dec 21 Stephen Rothwell
2015-12-21 17:37 ` Randy Dunlap [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=567838CE.1050301@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).