From: Kalle Valo <kvalo@codeaurora.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Simon Kelley <simon@thekelleys.org.uk>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: atmel: potential underflow in atmel_set_freq()
Date: Wed, 11 May 2016 19:03:34 +0000 (UTC) [thread overview]
Message-ID: <20160511190334.5797D61322@smtp.codeaurora.org> (raw)
In-Reply-To: <20160510192117.GC30712@mwanda>
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> Smatch complains that we cap the upper bound of "fwrq->m" but not the
> lower bound. I don't know if it can actually happen but it's simple
> enough to check for negatives.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Thanks, 1 patch applied to wireless-drivers-next.git:
d9739a26fbca atmel: potential underflow in atmel_set_freq()
--
Sent by pwcli
https://patchwork.kernel.org/patch/9061371/
prev parent reply other threads:[~2016-05-11 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 19:21 [patch] atmel: potential underflow in atmel_set_freq() Dan Carpenter
2016-05-11 19:03 ` Kalle Valo [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=20160511190334.5797D61322@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=simon@thekelleys.org.uk \
/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).