[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <22278785.Xzxnmu2YlU@wuerfel>
Date: Wed, 14 Oct 2015 17:38:35 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Eric Auger <eric.auger@...aro.org>, eric.auger@...com,
alex.williamson@...hat.com, b.reynal@...tualopensystems.com,
kvmarm@...ts.cs.columbia.edu, kvm@...r.kernel.org,
thomas.lendacky@....com, patches@...aro.org,
christoffer.dall@...aro.org, suravee.suthikulpanit@....com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] VFIO: platform: AMD xgbe reset module
On Wednesday 14 October 2015 15:33:12 Eric Auger wrote:
> --- a/drivers/vfio/platform/vfio_platform_common.c
> +++ b/drivers/vfio/platform/vfio_platform_common.c
> @@ -31,6 +31,11 @@ static const struct vfio_platform_reset_combo reset_lookup_table[] = {
> .reset_function_name = "vfio_platform_calxedaxgmac_reset",
> .module_name = "vfio-platform-calxedaxgmac",
> },
> + {
> + .compat = "amd,xgbe-seattle-v1a",
> + .reset_function_name = "vfio_platform_amdxgbe_reset",
> + .module_name = "vfio-platform-amdxgbe",
> + },
> };
>
> static void vfio_platform_get_reset(struct vfio_platform_device *vdev,
>
This is causing build errors for me when CONFIG_MODULES is disabled.
Could this please be restructured so vfio_platform_get_reset does
not attempt to call __symbol_get() but instead has the drivers
register themselves properly to a subsystem?
I don't see any way this could be fixed otherwise. The problem
of course showed up with calxedaxgmac already, but I'd prefer not
to see anything added there until the common code has been improved.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists