From: Lucas Stach <l.stach@pengutronix.de> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Luis R . Rodriguez" <mcgrof@kernel.org> Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org, Vinod Koul <vkoul@kernel.org>, kernel@pengutronix.de, patchwork-lst@pengutronix.de Subject: [v2,2/2] dmaengine: imx-sdma: don't print warning when firmware is absent Date: Mon, 12 Nov 2018 17:01:43 +0100 [thread overview] Message-ID: <20181112160143.4459-2-l.stach@pengutronix.de> (raw) The SDMA firmware is optional and a usable fallabck to the internal ROM firmware is present in the driver. There is already a message printed informing the user that the internal firmware is used, so there is no need to print a scary warning for what is normal operation on most systems. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> --- drivers/dma/imx-sdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c index b4ec2d20e661..c2e7819cecb8 100644 --- a/drivers/dma/imx-sdma.c +++ b/drivers/dma/imx-sdma.c @@ -1784,7 +1784,7 @@ static int sdma_get_firmware(struct sdma_engine *sdma, { int ret; - ret = request_firmware_nowait(THIS_MODULE, + ret = request_firmware_nowait_nowarn(THIS_MODULE, FW_ACTION_HOTPLUG, fw_name, sdma->dev, GFP_KERNEL, sdma, sdma_load_firmware);
WARNING: multiple messages have this Message-ID (diff)
From: Lucas Stach <l.stach@pengutronix.de> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, "Luis R . Rodriguez" <mcgrof@kernel.org> Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org, Vinod Koul <vkoul@kernel.org>, kernel@pengutronix.de, patchwork-lst@pengutronix.de Subject: [PATCH v2 2/2] dmaengine: imx-sdma: don't print warning when firmware is absent Date: Mon, 12 Nov 2018 17:01:43 +0100 [thread overview] Message-ID: <20181112160143.4459-2-l.stach@pengutronix.de> (raw) In-Reply-To: <20181112160143.4459-1-l.stach@pengutronix.de> The SDMA firmware is optional and a usable fallabck to the internal ROM firmware is present in the driver. There is already a message printed informing the user that the internal firmware is used, so there is no need to print a scary warning for what is normal operation on most systems. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> --- drivers/dma/imx-sdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c index b4ec2d20e661..c2e7819cecb8 100644 --- a/drivers/dma/imx-sdma.c +++ b/drivers/dma/imx-sdma.c @@ -1784,7 +1784,7 @@ static int sdma_get_firmware(struct sdma_engine *sdma, { int ret; - ret = request_firmware_nowait(THIS_MODULE, + ret = request_firmware_nowait_nowarn(THIS_MODULE, FW_ACTION_HOTPLUG, fw_name, sdma->dev, GFP_KERNEL, sdma, sdma_load_firmware); -- 2.19.1
next reply other threads:[~2018-11-12 16:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-12 16:01 Lucas Stach [this message] 2018-11-12 16:01 ` [PATCH v2 2/2] dmaengine: imx-sdma: don't print warning when firmware is absent Lucas Stach -- strict thread matches above, loose matches on Subject: below -- 2018-11-19 20:07 [v2,1/2] firmware: add nowarn variant of request_firmware_nowait() Luis R. Rodriguez 2018-11-19 20:07 ` [PATCH v2 1/2] " Luis Chamberlain 2018-11-12 16:01 [v2,1/2] " Lucas Stach 2018-11-12 16:01 ` [PATCH v2 1/2] " Lucas Stach
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=20181112160143.4459-2-l.stach@pengutronix.de \ --to=l.stach@pengutronix.de \ --cc=dmaengine@vger.kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=kernel@pengutronix.de \ --cc=linux-kernel@vger.kernel.org \ --cc=mcgrof@kernel.org \ --cc=patchwork-lst@pengutronix.de \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.