linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Vaibhav Hiremath <hvaibhav@ti.com>,
	Stanimir Varbanov <svarbanov@mm-sol.com>,
	Dominic Curran <dcurran@ti.com>, David Cohen <dacohen@gmail.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	llvm@lists.linux.dev
Subject: Re: [PATCH] media: omap3isp: fix out-of-range warning
Date: Thu, 25 Nov 2021 08:43:00 +0100	[thread overview]
Message-ID: <CAK8P3a2kEByuNJu9NMiD2m3v+K0acE-XwdevHGByi_82bko7Uw@mail.gmail.com> (raw)
In-Reply-To: <YZ68G09viJA/vkby@pendragon.ideasonboard.com>

On Wed, Nov 24, 2021 at 11:26 PM Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> On Wed, Nov 24, 2021 at 08:24:15PM +0100, Arnd Bergmann wrote:
> >
> > Add a cast to 32-bit to avoid the warning. Checking just the lower bounds
> > would be sufficient as well, but it seems more consistent to use
> > the IS_OUT_OF_BOUNDS() check for all members.
>
> Mauro has submitted a fix that handles the cast in the
> IS_OUT_OF_BOUNDS() macro, see
> https://lore.kernel.org/all/b70f819b11e024649f113be1158f34b24914a1ed.1637573097.git.mchehab+huawei@kernel.org/.

Ok, thanks. I've marked my patch as 'Obsoleted' in patchwork now.

      Arnd

      reply	other threads:[~2021-11-25  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 19:24 [PATCH] media: omap3isp: fix out-of-range warning Arnd Bergmann
2021-11-24 22:26 ` Laurent Pinchart
2021-11-25  7:43   ` Arnd Bergmann [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=CAK8P3a2kEByuNJu9NMiD2m3v+K0acE-XwdevHGByi_82bko7Uw@mail.gmail.com \
    --to=arnd@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dacohen@gmail.com \
    --cc=dcurran@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=svarbanov@mm-sol.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).