From: Dan Carpenter <dan.carpenter@oracle.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: Christopher Harrer <charrer@alacritech.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lior Dotan <liodot@gmail.com>,
devel@driverdev.osuosl.org, Julia Lawall <julia.lawall@lip6.fr>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging-slicoss: Use a signed return type for slic_card_locate()
Date: Sat, 19 Dec 2015 20:19:55 +0000 [thread overview]
Message-ID: <20151219201955.GS5284@mwanda> (raw)
In-Reply-To: <5675B207.2010706@users.sourceforge.net>
It returns zero or negative error codes. The callers expect int. It is
harmless. It should just be int.
regards,
dan carpenter
next prev parent reply other threads:[~2015-12-19 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 19:37 [PATCH] staging-slicoss: Use a signed return type for slic_card_locate() SF Markus Elfring
2015-12-19 20:19 ` Dan Carpenter [this message]
2015-12-22 14:12 ` [PATCH v2] " SF Markus Elfring
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=20151219201955.GS5284@mwanda \
--to=dan.carpenter@oracle.com \
--cc=charrer@alacritech.com \
--cc=devel@driverdev.osuosl.org \
--cc=elfring@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liodot@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 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).