From: Vinod Koul <vkoul@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: Gustavo Pimentel <Gustavo.Pimentel@synopsys.com>,
kbuild-all@01.org, Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: fix semicolon.cocci warnings
Date: Tue, 25 Jun 2019 09:59:56 +0530 [thread overview]
Message-ID: <20190625042956.GI2962@vkoul-mobl> (raw)
In-Reply-To: <20190615160550.GA59533@lkp-kbuild03>
On 16-06-19, 00:05, kbuild test robot wrote:
> From: kbuild test robot <lkp@intel.com>
>
> drivers/dma/dw-edma/dw-edma-core.c:617:2-3: Unneeded semicolon
>
>
> Remove unneeded semicolon.
>
> Generated by: scripts/coccinelle/misc/semicolon.cocci
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2019-06-25 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201906160043.LzDXUsKd%lkp@intel.com>
2019-06-15 16:05 ` [PATCH] dmaengine: fix semicolon.cocci warnings kbuild test robot
2019-06-21 8:43 ` Gustavo Pimentel
2019-06-25 4:29 ` Vinod Koul [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=20190625042956.GI2962@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=Gustavo.Pimentel@synopsys.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).