From: Michael Stickel <ms@mycable.de>
To: Michael Welling <mwelling@ieee.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Walleij <linus.walleij@linaro.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the gpio tree with Linus' tree
Date: Wed, 28 May 2014 17:34:05 +0200 [thread overview]
Message-ID: <538601ED.8030601@mycable.de> (raw)
In-Reply-To: <20140528133832.GA2541@deathray>
Am 28.05.2014 15:38, schrieb Michael Welling:
> Looking at the Linux next version, I am fairly certian that the following is
> redundant checking:
> if (chips < 0) {
> dev_err(&spi->dev, "FATAL: invalid negative chip id\n");
> goto fail;
> }
>
> The chips variable should equal the number of bits in the spi_present_mask variable.
> Or am I missing something?
Can be left out. Was just a paranoid check, because with the missing
increment in the of path it became negative.
--
------------------------------------------------------------------------
Michael Stickel Tel. +49 4321 559 56-29
mycable GmbH Fax +49 4321 559 56-10
Gartenstrasse 10
24534 Neumuenster, Germany Email ms@mycable.de
------------------------------------------------------------------------
mycable GmbH, Managing Director: Michael Carstens-Behrens
USt-IdNr: DE 214 231 199, Amtsgericht Kiel, HRB 1797 NM
------------------------------------------------------------------------
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. If you have received this e-mail in error,
please notify the sender and delete all copies from your system.
------------------------------------------------------------------------
next prev parent reply other threads:[~2014-05-28 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 9:00 linux-next: manual merge of the gpio tree with Linus' tree Stephen Rothwell
2014-05-28 13:38 ` Michael Welling
2014-05-28 15:34 ` Michael Stickel [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-01 4:03 Stephen Rothwell
2012-05-14 8:31 Stephen Rothwell
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=538601ED.8030601@mycable.de \
--to=ms@mycable.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mwelling@ieee.org \
--cc=sfr@canb.auug.org.au \
/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).