From: Borislav Petkov <bp@alien8.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Stuart Little <achirvasub@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
linux-nvdimm@lists.01.org,
kernel list <linux-kernel@vger.kernel.org>,
linux- stable <stable@vger.kernel.org>,
Adrian Huang <ahuang12@lenovo.com>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com, Ira Weiny <ira.weiny@intel.com>,
mpatocka@redhat.com, lkft-triage@lists.linaro.org,
Jan Kara <jack@suse.cz>
Subject: Re: PROBLEM: 5.9.0-rc6 fails to compile due to 'redefinition of ‘dax_supported’'
Date: Mon, 21 Sep 2020 10:02:58 +0200 [thread overview]
Message-ID: <20200921080258.GA5947@zn.tnic> (raw)
In-Reply-To: <20200921073218.GA3142611@kroah.com>
On Mon, Sep 21, 2020 at 09:32:18AM +0200, Greg KH wrote:
> all my local builds are breaking now too with this :(
>
> Was there a proposed patch anywhere for this?
I've disabled CONFIG_BLK_DEV_PMEM which allowed me to de-select those
two:
# CONFIG_DAX is not set
# CONFIG_FS_DAX is not set
and now it at least builds.
In order to avoid such breakage in the future, I'd suggest you guys to
run randconfigs on your stuff before sending, especially if the Kconfig
ifdeffery is not a trivial one like the DAX maze.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-09-21 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 1:03 PROBLEM: 5.9.0-rc6 fails to compile due to 'redefinition of ‘dax_supported’' Stuart Little
2020-09-21 2:25 ` Stuart Little
2020-09-21 3:50 ` Robert Gadsdon
2020-09-21 6:04 ` Naresh Kamboju
2020-09-21 7:32 ` Greg KH
2020-09-21 8:02 ` Borislav Petkov [this message]
2020-09-21 8:49 ` Bhaskar Chowdhury
2020-09-21 9:50 ` Jan Kara
2020-09-21 10:08 ` Geert Uytterhoeven
2020-09-21 10:29 ` Stuart Little
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=20200921080258.GA5947@zn.tnic \
--to=bp@alien8.de \
--cc=achirvasub@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dm-devel@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mpatocka@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=snitzer@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vishal.l.verma@intel.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