dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Dan Williams <dan.j.williams@intel.com>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: Re: [PATCH][next] dmaengine: ti: k3-udma: Use struct_size() in kzalloc()
Date: Wed, 24 Jun 2020 12:57:10 +0530	[thread overview]
Message-ID: <20200624072710.GK2324254@vkoul-mobl> (raw)
In-Reply-To: <fa304f0ef1dba4fcf5e495f3c2feb4d3816f20ac.camel@perches.com>

On 23-06-20, 22:56, Joe Perches wrote:
> On Wed, 2020-06-24 at 11:25 +0530, Vinod Koul wrote:
> > On 19-06-20, 17:43, Gustavo A. R. Silva wrote:
> > > Make use of the struct_size() helper instead of an open-coded version
> > > in order to avoid any potential type mistakes.
> > > 
> > > This code was detected with the help of Coccinelle and, audited and
> > > fixed manually.
> > > 
> > > Addresses-KSPP-ID: https://github.com/KSPP/linux/issues/83
> 
> Is this odd tag really useful?

Not at all :)

-- 
~Vinod

  reply	other threads:[~2020-06-24  7:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 22:43 [PATCH][next] dmaengine: ti: k3-udma: Use struct_size() in kzalloc() Gustavo A. R. Silva
2020-06-24  5:55 ` Vinod Koul
2020-06-24  5:56   ` Joe Perches
2020-06-24  7:27     ` Vinod Koul [this message]
2020-06-24  9:14   ` Peter Ujfalusi
2020-06-24 17:12   ` Gustavo A. R. Silva
2020-06-26  7:30     ` Peter Ujfalusi
2020-06-26 13:29       ` Gustavo A. R. Silva
2020-06-29  6:43         ` Peter Ujfalusi
2020-07-10 18:25           ` Gustavo A. R. Silva
2020-07-15  6:21             ` Vinod Koul
2020-07-15 14:06               ` Gustavo A. R. Silva

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=20200624072710.GK2324254@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=gustavo@embeddedor.com \
    --cc=gustavoars@kernel.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@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;
as well as URLs for NNTP newsgroup(s).