Re: [PATCH][-next] acpi/acpi_drivers.h: fix warnings when ACPI_DOCKis not enabled

From: Arnaud Lacombe
Date: Fri Aug 12 2011 - 20:23:48 EST


Hi,

On Fri, Jul 29, 2011 at 12:34 PM, Arnaud Lacombe <lacombar@xxxxxxxxx> wrote:
> /src/linux/linux/drivers/ata/libata-acpi.c: In function 'ata_acpi_associate':
> /src/linux/linux/drivers/ata/libata-acpi.c:266:11: warning: passing argument 2 of 'register_hotplug_dock_device' discards 'const' qualifier from pointer target type [enabled by default]
> /src/linux/linux/include/acpi/acpi_drivers.h:146:19: note: expected 'struct acpi_dock_ops *' but argument is of type 'const struct acpi_dock_ops *'
> /src/linux/linux/drivers/ata/libata-acpi.c:275:11: warning: passing argument 2 of 'register_hotplug_dock_device' discards 'const' qualifier from pointer target type [enabled by default]
> /src/linux/linux/include/acpi/acpi_drivers.h:146:19: note: expected 'struct acpi_dock_ops *' but argument is of type 'const struct acpi_dock_ops *'
>
ping ? next-20110811 is still bad.

- Arnaud

> Cc: Vasiliy Kulikov <segoon@xxxxxxxxxxxx>
> Cc: Jeff Garzik <jgarzik@xxxxxxxxxx>
> Cc: Len Brown <len.brown@xxxxxxxxx>
> Signed-off-by: Arnaud Lacombe <lacombar@xxxxxxxxx>
> ---
>  include/acpi/acpi_drivers.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/acpi/acpi_drivers.h b/include/acpi/acpi_drivers.h
> index e49c36d..bb145e4 100644
> --- a/include/acpi/acpi_drivers.h
> +++ b/include/acpi/acpi_drivers.h
> @@ -144,7 +144,7 @@ static inline void unregister_dock_notifier(struct notifier_block *nb)
>  {
>  }
>  static inline int register_hotplug_dock_device(acpi_handle handle,
> -                                              struct acpi_dock_ops *ops,
> +                                              const struct acpi_dock_ops *ops,
>                                               void *context)
>  {
>        return -ENODEV;
> --
> 1.7.6.153.g78432
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/