From: Julia Lawall <julia.lawall@inria.fr>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: kbuild-all@lists.01.org, Akhil R <akhilrajeev@nvidia.com>,
dan.j.williams@intel.com, devicetree@vger.kernel.org,
dmaengine@vger.kernel.org, jonathanh@nvidia.com,
kyarlagadda@nvidia.com, ldewangan@nvidia.com,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
p.zabel@pengutronix.de, rgumasta@nvidia.com
Subject: [PATCH] dmaengine: tegra: fix flexible_array.cocci warnings
Date: Fri, 26 Nov 2021 17:00:18 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2111261659030.18994@hadrien> (raw)
From: kernel test robot <lkp@intel.com>
Zero-length and one-element arrays are deprecated, see
Documentation/process/deprecated.rst
Flexible-array members should be used instead.
Generated by: scripts/coccinelle/misc/flexible_array.cocci
CC: Akhil R <akhilrajeev@nvidia.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
Signed-off-by: Julia Lawall <julia.lawall@inria.fr>
---
url: https://github.com/0day-ci/linux/commits/Akhil-R/Add-NVIDIA-Tegra-GPC-DMA-driver/20211122-173019
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
:::::: branch date: 29 hours ago
:::::: commit date: 29 hours ago
Please take the patch only if it's a positive warning. Thanks!
tegra186-gpc-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/dma/tegra186-gpc-dma.c
+++ b/drivers/dma/tegra186-gpc-dma.c
@@ -238,7 +238,7 @@ struct tegra_dma {
unsigned long sid_m2d_reserved;
unsigned long sid_d2m_reserved;
unsigned long sid_m2m_reserved;
- struct tegra_dma_channel channels[0];
+ struct tegra_dma_channel channels[];
};
static inline void tdc_write(struct tegra_dma_channel *tdc,
reply other threads:[~2021-11-26 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.22.394.2111261659030.18994@hadrien \
--to=julia.lawall@inria.fr \
--cc=akhilrajeev@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rgumasta@nvidia.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