From: Grygorii Strashko <grygorii.strashko@ti.com>
To: kernel test robot <lkp@intel.com>
Cc: <kbuild-all@lists.01.org>, <linux-kernel@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Tero Kristo <t-kristo@ti.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] soc: ti: k3: fix semicolon.cocci warnings
Date: Fri, 26 Jun 2020 13:48:16 +0300 [thread overview]
Message-ID: <b5cd53c9-1288-2050-a7b6-f07f8e2fb5bf@ti.com> (raw)
In-Reply-To: <20200623183416.GA6477@aae0707f33c9>
On 23/06/2020 21:34, kernel test robot wrote:
> From: kernel test robot <lkp@intel.com>
>
> drivers/soc/ti/k3-ringacc.c:616:2-3: Unneeded semicolon
>
>
> Remove unneeded semicolon.
>
> Generated by: scripts/coccinelle/misc/semicolon.cocci
>
> Fixes: 3277e8aa2504 ("soc: ti: k3: add navss ringacc driver")
> CC: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: kernel test robot <lkp@intel.com>
> ---
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 3e08a95294a4fb3702bb3d35ed08028433c37fe6
> commit: 3277e8aa2504d97e022ecb9777d784ac1a439d36 soc: ti: k3: add navss ringacc driver
>
> k3-ringacc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- a/drivers/soc/ti/k3-ringacc.c
> +++ b/drivers/soc/ti/k3-ringacc.c
> @@ -613,7 +613,7 @@ int k3_ringacc_ring_cfg(struct k3_ring *
> ring->ops = NULL;
> ret = -EINVAL;
> goto err_free_proxy;
> - };
> + }
>
> ring->ring_mem_virt = dma_alloc_coherent(ringacc->dev,
> ring->size * (4 << ring->elm_size),
>
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
--
Best regards,
grygorii
prev parent reply other threads:[~2020-06-26 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 18:34 drivers/soc/ti/k3-ringacc.c:616:2-3: Unneeded semicolon kernel test robot
2020-06-23 18:34 ` [PATCH] soc: ti: k3: fix semicolon.cocci warnings kernel test robot
2020-06-26 10:48 ` Grygorii Strashko [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=b5cd53c9-1288-2050-a7b6-f07f8e2fb5bf@ti.com \
--to=grygorii.strashko@ti.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=peter.ujfalusi@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=t-kristo@ti.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
all inboxes | Powered by JetHome®