All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Baolin Wang <baolin.wang@linaro.org>,
	Orson Zhai <orsonzhai@gmail.com>,
	Chunyan Zhang <zhang.lyra@gmail.com>,
	dmaengine@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: dmaengine: sprd: fix an NULL vs IS_ERR() bug
Date: Thu, 17 May 2018 10:01:05 +0530	[thread overview]
Message-ID: <20180517043105.GR13271@vkoul-mobl> (raw)

On 16-05-18, 11:48, Dan Carpenter wrote:
> We recently cleaned this code up but we need to update the error
> handling as well.  The devm_ioremap_resource() returns error pointers on
> error, never NULL.

Applied, thanks

WARNING: multiple messages have this Message-ID (diff)
From: Vinod <vkoul@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Baolin Wang <baolin.wang@linaro.org>,
	Orson Zhai <orsonzhai@gmail.com>,
	Chunyan Zhang <zhang.lyra@gmail.com>,
	dmaengine@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] dmaengine: sprd: fix an NULL vs IS_ERR() bug
Date: Thu, 17 May 2018 04:43:05 +0000	[thread overview]
Message-ID: <20180517043105.GR13271@vkoul-mobl> (raw)
In-Reply-To: <20180516084807.GA23043@mwanda>

On 16-05-18, 11:48, Dan Carpenter wrote:
> We recently cleaned this code up but we need to update the error
> handling as well.  The devm_ioremap_resource() returns error pointers on
> error, never NULL.

Applied, thanks

-- 
~Vinod

             reply	other threads:[~2018-05-17  4:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17  4:31 Vinod Koul [this message]
2018-05-17  4:43 ` [PATCH] dmaengine: sprd: fix an NULL vs IS_ERR() bug Vinod
  -- strict thread matches above, loose matches on Subject: below --
2018-05-16  8:56 Baolin Wang
2018-05-16  8:56 ` [PATCH] " Baolin Wang
2018-05-16  8:48 Dan Carpenter
2018-05-16  8:48 ` [PATCH] " Dan Carpenter

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=20180517043105.GR13271@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=baolin.wang@linaro.org \
    --cc=dan.carpenter@oracle.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=orsonzhai@gmail.com \
    --cc=zhang.lyra@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.