From: Julia Lawall <julia.lawall@lip6.fr>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Julia Lawall <Julia.Lawall@lip6.fr>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
kernel-janitors@vger.kernel.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/10] video: use safer test on the result of find_first_zero_bit
Date: Mon, 23 Jun 2014 14:12:41 +0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1406231612030.3905@hadrien> (raw)
In-Reply-To: <53A81470.5030606@ti.com>
On Mon, 23 Jun 2014, Tomi Valkeinen wrote:
> On 04/06/14 12:07, Julia Lawall wrote:
> > From: Julia Lawall <Julia.Lawall@lip6.fr>
> >
> > Find_first_zero_bit considers BITS_PER_LONG bits at a time, and thus may
> > return a larger number than the maximum position argument if that position
> > is not a multiple of BITS_PER_LONG.
>
> Thanks, queued for 3.17.
No, sorry you can drop it. It doesn't hurt anything, but it is not
necessary either. Returning a larger number is actually not possible.
julia
next prev parent reply other threads:[~2014-06-23 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 9:07 [PATCH 0/10] use safer test on the result of find_first_zero_bit Julia Lawall
2014-06-04 9:07 ` [PATCH 3/10] video: " Julia Lawall
2014-06-23 11:50 ` Tomi Valkeinen
2014-06-23 14:12 ` Julia Lawall [this message]
2014-06-24 7:56 ` Tomi Valkeinen
2014-06-04 9:35 ` [PATCH 0/10] " Geert Uytterhoeven
[not found] ` <CAMuHMdXsoFUXj4jLMWN6NY7Um19KwWO9Rhx=9=gqWu_K5Ev2kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-04 9:38 ` Julia Lawall
2014-06-04 9:46 ` David Laight
2014-06-04 9:52 ` Julia Lawall
2014-06-04 10:55 ` Geert Uytterhoeven
2014-06-04 11:00 ` Julia Lawall
2014-06-04 11:07 ` Geert Uytterhoeven
2014-06-04 13:12 ` Julia Lawall
2014-06-04 13:34 ` David Laight
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=alpine.DEB.2.10.1406231612030.3905@hadrien \
--to=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.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