From: Vinod Koul <vkoul@kernel.org>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
dan.j.williams@intel.com, linux-arm-msm@vger.kernel.org,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: qcom: remove unneeded semicolon
Date: Wed, 3 Feb 2021 17:00:59 +0530 [thread overview]
Message-ID: <20210203113059.GQ2771@vkoul-mobl> (raw)
In-Reply-To: <1612248373-43529-1-git-send-email-yang.lee@linux.alibaba.com>
On 02-02-21, 14:46, Yang Li wrote:
> Eliminate the following coccicheck warning:
> ./drivers/dma/qcom/gpi.c:1703:2-3: Unneeded semicolon
This was already fixed with commit 9ee8f3d968ae3dd838c379da7c9bfd335dbdcd95
--
~Vinod
next prev parent reply other threads:[~2021-02-03 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 6:46 [PATCH] dmaengine: qcom: remove unneeded semicolon Yang Li
2021-02-03 11:30 ` Vinod Koul [this message]
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm
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=20210203113059.GQ2771@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yang.lee@linux.alibaba.com \
/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