mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Mark Gross <markgross@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform: olpc: use SPI device ID data to bind device
Date: Mon, 20 Mar 2023 14:50:20 +0100	[thread overview]
Message-ID: <22d2e345-3640-c8b4-e913-204f1d96dde3@redhat.com> (raw)
In-Reply-To: <20230316160324.78856-1-krzysztof.kozlowski@linaro.org>

Hi,

On 3/16/23 17:03, Krzysztof Kozlowski wrote:
> The driver defines spi_device_id table for module autoloading, but does
> not use it in id_table which causes W=1 warning:
> 
>   drivers/platform/olpc/olpc-xo175-ec.c:737:35: error: ‘olpc_xo175_ec_id_table’ defined but not used [-Werror=unused-const-variable=]
> 
> Reference the SPI device ID table, so it can be also used for device
> binding.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Thank you for your patch, I've applied this patch to my review-hans 
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans

Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.

Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.

Regards,

Hans


> 
> ---
> 
> Changes since v1:
> 1. Rework the patch - reference the ID table instead of __maybe_unused.
> ---
>  drivers/platform/olpc/olpc-xo175-ec.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/platform/olpc/olpc-xo175-ec.c b/drivers/platform/olpc/olpc-xo175-ec.c
> index 4823bd2819f6..62ccbcb15c74 100644
> --- a/drivers/platform/olpc/olpc-xo175-ec.c
> +++ b/drivers/platform/olpc/olpc-xo175-ec.c
> @@ -746,6 +746,7 @@ static struct spi_driver olpc_xo175_ec_spi_driver = {
>  		.of_match_table = olpc_xo175_ec_of_match,
>  		.pm = &olpc_xo175_ec_pm_ops,
>  	},
> +	.id_table	= olpc_xo175_ec_id_table,
>  	.probe		= olpc_xo175_ec_probe,
>  	.remove		= olpc_xo175_ec_remove,
>  };


      reply	other threads:[~2023-03-20 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 16:03 Krzysztof Kozlowski
2023-03-20 13:50 ` Hans de Goede [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=22d2e345-3640-c8b4-e913-204f1d96dde3@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®