From: Kevin Hilman <khilman@baylibre.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: ben-linux@fluff.org, ulf.hansson@linaro.org,
adrian.hunter@intel.com, vireshk@kernel.org,
maxime.ripard@free-electrons.com, wens@csie.org,
linux@armlinux.org.uk, carlo@caione.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 1/6 v3] mmc: meson-gx-mmc: Fix platform_get_irq's error checking
Date: Wed, 06 Dec 2017 16:58:27 -0800 [thread overview]
Message-ID: <7h4lp3mk0c.fsf@baylibre.com> (raw)
In-Reply-To: <c1c27676e9f141ace1254b40807bf2dc03f072c6.1511066652.git.arvind.yadav.cs@gmail.com> (Arvind Yadav's message of "Sun, 19 Nov 2017 10:22:43 +0530")
Arvind Yadav <arvind.yadav.cs@gmail.com> writes:
> The platform_get_irq() function returns negative if an error occurs.
> zero or positive number on success. platform_get_irq() error checking
> for zero is not correct.
>
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
Acked-by: Kevin Hilman <khilman@baylibre.com>
next prev parent reply other threads:[~2017-12-07 0:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 4:52 [PATCH 1/6 v3] mmc: meson-gx-mmc: Fix platform_get_irq's error checking Arvind Yadav
2017-11-19 4:52 ` [PATCH 2/6 v3] mmc: s3cmci: " Arvind Yadav
2017-12-15 9:17 ` Ulf Hansson
2017-11-19 4:52 ` [PATCH 3/6 v3] mmc: sdhci-acpi: Handle return value of platform_get_irq Arvind Yadav
2017-11-22 12:02 ` Adrian Hunter
2017-12-15 9:17 ` Ulf Hansson
2017-11-19 4:52 ` [PATCH 4/6 v3] mmc: sdhci-spear: " Arvind Yadav
2017-11-20 6:45 ` Viresh Kumar
2017-12-15 9:17 ` Ulf Hansson
2017-11-19 4:52 ` [PATCH 6/6 v3] mmc: sunxi-mmc: " Arvind Yadav
2017-12-15 9:18 ` Ulf Hansson
2017-12-07 0:58 ` Kevin Hilman [this message]
2017-12-15 9:17 ` [PATCH 1/6 v3] mmc: meson-gx-mmc: Fix platform_get_irq's error checking Ulf Hansson
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=7h4lp3mk0c.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=adrian.hunter@intel.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=ben-linux@fluff.org \
--cc=carlo@caione.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.ripard@free-electrons.com \
--cc=ulf.hansson@linaro.org \
--cc=vireshk@kernel.org \
--cc=wens@csie.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