From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] phy: allwinner: allow compile testing
Date: Tue, 5 Mar 2019 09:44:13 +0100 [thread overview]
Message-ID: <20190305084413.hthto7doaafwb2xy@flea> (raw)
In-Reply-To: <20190304202406.1716350-1-arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Mon, Mar 04, 2019 at 09:23:56PM +0100, Arnd Bergmann wrote:
> Some allwinner specific drivers can be built for testing purposes
> on non-sunxi configurations, which then results in a harmless
> warning:
>
> WARNING: unmet direct dependencies detected for PHY_SUN6I_MIPI_DPHY
> Depends on [n]: ARCH_SUNXI [=n] && HAS_IOMEM [=y] && OF [=y] && RESET_CONTROLLER [=y]
> Selected by [y]:
> - DRM_SUN6I_DSI [=y] && HAS_IOMEM [=y] && DRM_SUN4I [=y]
>
> Allow compile-test here as well to avoid the warning, and improve
> overall build coverage.
>
> Fixes: 5d134abf9530 ("phy: Move Allwinner A31 D-PHY driver to drivers/phy/")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2019-03-05 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 20:23 [PATCH 1/3] phy: allwinner: allow compile testing Arnd Bergmann
2019-03-04 20:23 ` [PATCH 2/3] phy: ti: usb2: fix OMAP_CONTROL_PHY dependency Arnd Bergmann
2019-03-04 20:23 ` [PATCH 3/3] phy: mapphone-mdm6600: add gpiolib dependency Arnd Bergmann
2019-03-05 15:46 ` Tony Lindgren
2019-03-05 8:44 ` Maxime Ripard [this message]
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=20190305084413.hthto7doaafwb2xy@flea \
--to=maxime.ripard@bootlin.com \
--cc=arnd@arndb.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.kocialkowski@bootlin.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;
as well as URLs for NNTP newsgroup(s).