linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Vasyl Gomonovych <gomonovych@gmail.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: cppi41: Fix channel queues array size check
Date: Fri, 22 Dec 2017 17:47:20 +0530	[thread overview]
Message-ID: <20171222121720.GU18649@localhost> (raw)
In-Reply-To: <1513871584-8783-1-git-send-email-gomonovych@gmail.com>

On Thu, Dec 21, 2017 at 09:23:04PM +0530, Vasyl Gomonovych wrote:
> The test should be >= ARRAY_SIZE() instead of > ARRAY_SIZE().

Applied, thanks

-- 
~Vinod

      reply	other threads:[~2017-12-22 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 15:53 [PATCH] dmaengine: cppi41: Fix channel queues array size check Vasyl Gomonovych
2017-12-22 12:17 ` 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=20171222121720.GU18649@localhost \
    --to=vinod.koul@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=gomonovych@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).