From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] media: vsp1: cleanup a false positive warning
Date: Fri, 4 May 2018 12:32:18 -0300 [thread overview]
Message-ID: <20180504123218.2f900409@vento.lan> (raw)
In-Reply-To: <CAMuHMdX-kD0a_bRnxB+G8eE6sVhETAGuyoYOr5N0HM9VZa8LCw@mail.gmail.com>
Em Fri, 4 May 2018 16:37:23 +0200
Geert Uytterhoeven <geert@linux-m68k.org> escreveu:
> Hi Mauro,
>
> On Fri, May 4, 2018 at 2:13 PM, Mauro Carvalho Chehab
> <mchehab+samsung@kernel.org> wrote:
> > With the new vsp1 code changes introduced by changeset
> > f81f9adc4ee1 ("media: v4l: vsp1: Assign BRU and BRS to pipelines dynamically"),
> > smatch complains with:
> > drivers/media/platform/vsp1/vsp1_drm.c:262 vsp1_du_pipeline_setup_bru() error: we previously assumed 'pipe->bru' could be null (see line 180)
> >
> > This is a false positive, as, if pipe->bru is NULL, the brx
> > var will be different, with ends by calling a code that will
> > set pipe->bru to another value.
> >
> > Yet, cleaning this false positive is as easy as adding an explicit
> > check if pipe->bru is NULL.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
>
> Thanks for your patch!
>
> s/bru/brx/
Hah, yeah... there was a rename from bru->brx...
I guess that confused me, as I saw this error before the renaming patch
(even though I wrote it to be applied after them) :-)
>
> > --- a/drivers/media/platform/vsp1/vsp1_drm.c
> > +++ b/drivers/media/platform/vsp1/vsp1_drm.c
> > @@ -185,7 +185,7 @@ static int vsp1_du_pipeline_setup_brx(struct vsp1_device *vsp1,
> > brx = &vsp1->brs->entity;
> >
> > /* Switch BRx if needed. */
> > - if (brx != pipe->brx) {
> > + if (brx != pipe->brx || !pipe->brx) {
> > struct vsp1_entity *released_brx = NULL;
> >
> > /* Release our BRx if we have one. */
>
> Gr{oetje,eeting}s,
>
> Geert
>
Thanks,
Mauro
next prev parent reply other threads:[~2018-05-04 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 12:13 [PATCH] media: vsp1: cleanup a false positive warning Mauro Carvalho Chehab
2018-05-04 12:13 ` Mauro Carvalho Chehab
2018-05-04 14:37 ` Geert Uytterhoeven
2018-05-04 15:32 ` Mauro Carvalho Chehab [this message]
2018-05-07 14:05 ` Laurent Pinchart
2018-05-07 15:21 ` Mauro Carvalho Chehab
2018-08-08 13:58 ` Mauro Carvalho Chehab
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=20180504123218.2f900409@vento.lan \
--to=mchehab+samsung@kernel.org \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.