From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Kim Seer Paller <kimseer.paller@analog.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [linux-next:master 2315/3762] drivers/iio/adc/max14001.c:81:29: sparse: sparse: incorrect type in initializer (different base types)
Date: Thu, 20 Jul 2023 19:30:27 +0300 [thread overview]
Message-ID: <CAHp75VfKuvcih6ZZ3yiOEO0E=GF_g7E-kWVocdeWQ6L-pXkjZg@mail.gmail.com> (raw)
In-Reply-To: <202307210041.jT6femhS-lkp@intel.com>
On Thu, Jul 20, 2023 at 7:14 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: c58c49dd89324b18a812762a2bfa5a0458e4f252
> commit: ba2c3e63b681b624e0158775620ee2f89cc7e266 [2315/3762] iio: adc: max14001: New driver
> config: arc-randconfig-r093-20230720 (https://download.01.org/0day-ci/archive/20230721/202307210041.jT6femhS-lkp@intel.com/config)
> compiler: arc-elf-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230721/202307210041.jT6femhS-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202307210041.jT6femhS-lkp@intel.com/
Exactly why I asked to elaborate on the algorithm documentation and
hence developing proper driver updates to fix this issue in
particular.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-07-20 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 16:12 kernel test robot
2023-07-20 16:30 ` Andy Shevchenko [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='CAHp75VfKuvcih6ZZ3yiOEO0E=GF_g7E-kWVocdeWQ6L-pXkjZg@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=kimseer.paller@analog.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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