From: <Tudor.Ambarus@microchip.com>
To: <Claudiu.Beznea@microchip.com>, <Ludovic.Desroches@microchip.com>,
<vkoul@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lkp@intel.com>
Subject: Re: [PATCH] dmaengine: at_xdmac: fix compilation warning
Date: Mon, 25 Oct 2021 08:34:24 +0000 [thread overview]
Message-ID: <ef3f66d0-f07f-cf87-fa9c-c4ab4e565ac7@microchip.com> (raw)
In-Reply-To: <20211025074002.722504-1-claudiu.beznea@microchip.com>
On 10/25/21 10:40 AM, Claudiu Beznea wrote:
> Fixed "unused variable 'atmel_xdmac_dev_pm_ops'" compilation warning
> when CONFIG_PM is not defined.
>
> Fixes: 8e0c7e486014 ("dmaengine: at_xdmac: use pm_ptr()")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
> drivers/dma/at_xdmac.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/at_xdmac.c b/drivers/dma/at_xdmac.c
> index 7fb19bd18ac3..f5d053df66a5 100644
> --- a/drivers/dma/at_xdmac.c
> +++ b/drivers/dma/at_xdmac.c
> @@ -2207,7 +2207,7 @@ static int at_xdmac_remove(struct platform_device *pdev)
> return 0;
> }
>
> -static const struct dev_pm_ops atmel_xdmac_dev_pm_ops = {
> +static const struct dev_pm_ops __maybe_unused atmel_xdmac_dev_pm_ops = {
> .prepare = atmel_xdmac_prepare,
> SET_LATE_SYSTEM_SLEEP_PM_OPS(atmel_xdmac_suspend, atmel_xdmac_resume)
> };
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-25 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 7:40 [PATCH] dmaengine: at_xdmac: fix compilation warning Claudiu Beznea
2021-10-25 8:34 ` Tudor.Ambarus [this message]
2021-10-28 17:22 ` Vinod Koul
2021-12-08 10:41 ` Nicolas Ferre
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=ef3f66d0-f07f-cf87-fa9c-c4ab4e565ac7@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).