From: Tejun Heo <tj@kernel.org>
To: Dmitry Torokhov <dtor@chromium.org>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Wolfram Sang <wsa@the-dreams.de>, Joe Perches <joe@perches.com>,
Paul Bolle <pebolle@tiscali.nl>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sata_fsl: fix error handling of irq_of_parse_and_map
Date: Tue, 2 Dec 2014 13:00:37 -0500 [thread overview]
Message-ID: <20141202180037.GG10918@htj.dyndns.org> (raw)
In-Reply-To: <20141114213905.GA25228@dtor-ws>
On Fri, Nov 14, 2014 at 01:39:05PM -0800, Dmitry Torokhov wrote:
> irq_of_parse_and_map() returns 0 on error (the result is unsigned int),
> so testing for negative result never works.
>
> Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Sorry about the delay. Applied to libata/for-3.18-fixes w/ stable
cc'd.
Thanks.
--
tejun
prev parent reply other threads:[~2014-12-02 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 21:39 [PATCH] sata_fsl: fix error handling of irq_of_parse_and_map Dmitry Torokhov
2014-12-02 18:00 ` Tejun Heo [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=20141202180037.GG10918@htj.dyndns.org \
--to=tj@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=dtor@chromium.org \
--cc=joe@perches.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=wsa@the-dreams.de \
/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).