From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dan Williams <dan.j.williams@intel.com>, Jan Kara <jack@suse.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-xfs@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dax: hide block device code in #ifdef
Date: Mon, 15 May 2017 08:50:12 -0700 [thread overview]
Message-ID: <20170515155012.GM4519@birch.djwong.org> (raw)
In-Reply-To: <CAK8P3a1XU32oVTeV5=TeV8C+66rKKoRJnebQTAzqUr1BcSH69w@mail.gmail.com>
On Mon, May 15, 2017 at 04:20:09PM +0200, Arnd Bergmann wrote:
> On Mon, May 15, 2017 at 4:11 PM, Dan Williams <dan.j.williams@intel.com> wrote:
> > On Mon, May 15, 2017 at 6:44 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> We allow configurations with CONFIG_BLOCK=n and CONFIG_DAX=y, which now
> >> results in a link error:
> >>
> >> drivers/dax/super.c: In function 'bdev_dax_pgoff':
> >> drivers/dax/super.c:50:26: error: implicit declaration of function 'get_start_sect'; did you mean 'get_task_cred'? [-Werror=implicit-function-declaration]
> >>
> >> The two obvious ways to avoid the link error are to either add an #ifdef
> >> around the code that was moved from fs/block_dev.c, or to disallow the
> >> configuration. I could not see if there is or is not a reason to support
> >> this combination of options, but in case there is, the #ifdef is the
> >> safer choice.
> >>
> >> Fixes: ef51042472f5 ("block, dax: move "select DAX" from BLOCK to FS_DAX")
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >
> > Yup, the same one I came up with:
> >
> > https://patchwork.kernel.org/patch/9725513/
> >
> > If you have a a pull request coming up soon you can add my Acked-by to
> > both of these patches, otherwise I'll send what I have along at the
> > end of the week.
>
> I didn't plan to send a pull request, please use whatever you have.
I don't mind pulling the (second) patch in via the xfs tree.
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-15 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 13:44 Arnd Bergmann
2017-05-15 13:44 ` [PATCH 2/2] fs: xfs: add DAX dependency Arnd Bergmann
2017-05-15 14:11 ` [PATCH 1/2] dax: hide block device code in #ifdef Dan Williams
2017-05-15 14:20 ` Arnd Bergmann
2017-05-15 15:50 ` Darrick J. Wong [this message]
2017-05-16 11:16 ` Arnd Bergmann
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=20170515155012.GM4519@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=geert@linux-m68k.org \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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
all inboxes | Powered by JetHome®