From: Lee Jones <lee.jones@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Boris Brezillon <bbrezillon@kernel.org>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: linux-next: Tree for Mar 27 (sunxi clk & mfd)
Date: Mon, 1 Apr 2019 11:27:32 +0100 [thread overview]
Message-ID: <20190401102732.GD4187@dell> (raw)
In-Reply-To: <20190328095036.734adbba@canb.auug.org.au>
On Thu, 28 Mar 2019, Stephen Rothwell wrote:
> Hi Randy,
>
> On Wed, 27 Mar 2019 13:32:26 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > on i386 or x86_64:
> >
> > WARNING: unmet direct dependencies detected for MFD_SUN6I_PRCM
> > Depends on [n]: HAS_IOMEM [=y] && ARCH_SUNXI
> > Selected by [y]:
> > - CLK_SUNXI_PRCM_SUN8I [=y] && COMMON_CLK [=y] && CLK_SUNXI [=y]
>
> I reported that a while ago (x86_64 allmodconfig after the merge of the
> sunxi tree). Apparently there is a fix out there but it hasn't been
> applied yet.
Where is the fix to be applied? SUNXI or MFD?
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-04-01 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 3:50 linux-next: Tree for Mar 27 Stephen Rothwell
2019-03-27 20:32 ` linux-next: Tree for Mar 27 (sunxi clk & mfd) Randy Dunlap
2019-03-27 22:50 ` Stephen Rothwell
2019-04-01 10:27 ` Lee Jones [this message]
2019-04-01 11:36 ` Stephen Rothwell
2019-04-01 12:33 ` Maxime Ripard
2019-04-03 10:02 ` Lee Jones
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=20190401102732.GD4187@dell \
--to=lee.jones@linaro.org \
--cc=bbrezillon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.