From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
kbuild@lists.01.org, kbuild test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [sailus-media-tree:master 55/60] drivers/media/i2c/adv7180.c:573 adv7180_test_pattern() error: uninitialized symbol 'reg'.
Date: Fri, 29 Apr 2022 14:27:06 +0300 [thread overview]
Message-ID: <YmvLio/xAD4OSgeY@paasikivi.fi.intel.com> (raw)
In-Reply-To: <CAOMZO5A-ZbMUM-17n2JPN2+w+DWLL9fnGwo2SrS=O024M4v0MQ@mail.gmail.com>
On Fri, Apr 29, 2022 at 07:57:41AM -0300, Fabio Estevam wrote:
> Hi Dan,
>
> On Fri, Apr 29, 2022 at 7:30 AM Dan Carpenter <dan.carpenter@oracle.com> wrote:
> >
> > tree: git://linuxtv.org/sailus/media_tree.git master
> > head: ea1280040a678f38a4ce6f1817933c04cfe74552
> > commit: f3b4b140d87dc7f256229f20a8d70429a7549aca [55/60] media: i2c: adv7180: Add support for the test patterns
> > config: microblaze-randconfig-m031-20220427 (https://download.01.org/0day-ci/archive/20220429/202204290610.SVJgr8qV-lkp@intel.com/config)
> > compiler: microblaze-linux-gcc (GCC) 11.3.0
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> >
> > smatch warnings:
> > drivers/media/i2c/adv7180.c:573 adv7180_test_pattern() error: uninitialized symbol 'reg'.
>
> Thanks for the report.
>
> This problem has been resolved in v3:
>
> https://patchwork.linuxtv.org/project/linux-media/patch/20220427135025.3036234-1-festevam@gmail.com/
Yeah, my bad. I accidentally took v2. That's fixed now.
--
Sakari Ailus
prev parent reply other threads:[~2022-04-29 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 10:30 Dan Carpenter
2022-04-29 10:57 ` Fabio Estevam
2022-04-29 11:27 ` Sakari Ailus [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=YmvLio/xAD4OSgeY@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=festevam@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®