From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mmarek@suse.com, Peter Chen <peter.chen@freescale.com>,
Randy Dunlap <rdunlap@infradead.org>,
Joern Engel <joern@logfs.org>,
Prasad Joshi <prasadjoshi.linux@gmail.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] logfs: clarify MTD dependency
Date: Wed, 13 Jan 2016 21:45:05 +0100 [thread overview]
Message-ID: <6116283.ubGS0D0e49@wuerfel> (raw)
In-Reply-To: <20160113123918.544497b48bf4c03591c75747@linux-foundation.org>
On Wednesday 13 January 2016 12:39:18 Andrew Morton wrote:
>
> Randy's "logfs: fix logfs build errors and dependencies" is an
> only-in-mm thing. So it would make sense to combine the two patches
> into a single one and to give that an appropriate changelog.
>
> How does this look? (Primary author was chosen randomly)
>
>
> From: Arnd Bergmann <arnd@arndb.de>
> Subject: logfs: fix logfs build errors and dependencies
>
> Fix build errors that happen when CONFIG_LOGFS=y and CONFIG_MTD=m:
>
> fs/built-in.o: In function `logfs_mount':
> super.c:(.text+0x92a6f): undefined reference to `logfs_get_sb_mtd'
> fs/built-in.o: In function `logfs_get_sb_bdev':
> (.text+0x93530): undefined reference to `logfs_get_sb_mtd'
>
> This patch avoids the error by changing the dependencies of
> logfs in a way that we can no longer configure logfs as built-in
> when the MTD core is a loadable module, while leaving the
> dependency to require at least one of MTD or BLOCK to be
> enabled.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Michal Marek <mmarek@suse.cz>
> Cc: Peter Chen <peter.chen@freescale.com>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: Joern Engel <joern@logfs.org>
> Cc: Prasad Joshi <prasadjoshi.linux@gmail.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>
Looks good, thanks!
Arnd
next prev parent reply other threads:[~2016-01-13 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 13:25 [PATCH] logfs: clarify MTD dependency Arnd Bergmann
2016-01-13 20:39 ` Andrew Morton
2016-01-13 20:45 ` Arnd Bergmann [this message]
2016-01-13 21:31 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2015-11-27 13:54 Arnd Bergmann
2015-11-27 14:14 ` Michal Marek
2015-11-27 14:30 ` Arnd Bergmann
2015-11-27 14:50 ` Michal Marek
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=6116283.ubGS0D0e49@wuerfel \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=joern@logfs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=peter.chen@freescale.com \
--cc=prasadjoshi.linux@gmail.com \
--cc=rdunlap@infradead.org \
/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