From: Bjorn Andersson <bjorn.andersson@linaro•org>
To: Mark Brown <broonie@kernel•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
linux-kbuild@vger•kernel.org,
"Yann E. MORIN" <yann.morin.1998@free•fr>,
linux-remoteproc@vger•kernel.org,
Ohad Ben-Cohen <ohad@wizery•com>
Subject: Re: linux-next: build warning after merge of the regmap tree
Date: Mon, 6 Nov 2017 22:01:11 -0800 [thread overview]
Message-ID: <20171107060111.GV28761@minitux> (raw)
In-Reply-To: <20171106112143.ht4cmm2qngdbmmuy@sirena.co.uk>
On Mon 06 Nov 03:21 PST 2017, Mark Brown wrote:
> On Mon, Nov 06, 2017 at 03:30:37PM +1100, Stephen Rothwell wrote:
> > On Mon, 6 Nov 2017 15:21:57 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > > On Mon, 6 Nov 2017 11:52:14 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> > > > After merging the regmap tree, today's linux-next build
> > > > (arm_multi_v7_defconfig) produced this warning:
>
[..]
> isn't one right now. The root issue here is that HWSPINLOCK can be
> built modular which makes it very painful to use from core code.
I've picked Baolin's patch for making the hwspinlock core bool.
Hopefully this help avoid this issue. Looks like I missed today's
linux-next though.
Regards,
Bjorn
next prev parent reply other threads:[~2017-11-07 6:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 0:52 linux-next: build warning after merge of the regmap tree Stephen Rothwell
2017-11-06 4:21 ` Stephen Rothwell
2017-11-06 4:30 ` Stephen Rothwell
2017-11-06 11:21 ` Mark Brown
2017-11-07 6:01 ` Bjorn Andersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-06 0:54 Stephen Rothwell
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=20171107060111.GV28761@minitux \
--to=bjorn.andersson@linaro$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-remoteproc@vger$(echo .)kernel.org \
--cc=ohad@wizery$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=yann.morin.1998@free$(echo .)fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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