linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Robert Budai <robert.budai@analog.com>,
	Nuno Sa <nuno.sa@analog.com>,
	Ramona Gradinariu <ramona.gradinariu@analog.com>,
	Antoniu Miclaus <antoniu.miclaus@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Alex Lanzano <lanzano.alex@gmail.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4 5/6] iio: imu: adis16550: add adis16550 support
Date: Sun, 12 Jan 2025 15:33:58 +0000	[thread overview]
Message-ID: <20250112153358.16631b46@jic23-huawei> (raw)
In-Reply-To: <202501111951.NHXp98OK-lkp@intel.com>

On Sat, 11 Jan 2025 20:03:22 +0800
kernel test robot <lkp@intel.com> wrote:

> Hi Robert,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on jic23-iio/togreg]
> [also build test ERROR on linus/master v6.13-rc6 next-20250110]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Robert-Budai/iio-imu-adis-Add-custom-ops-struct/20250110-154645
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
> patch link:    https://lore.kernel.org/r/20250110074254.38966-6-robert.budai%40analog.com
> patch subject: [PATCH v4 5/6] iio: imu: adis16550: add adis16550 support
> config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20250111/202501111951.NHXp98OK-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250111/202501111951.NHXp98OK-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/202501111951.NHXp98OK-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>    In file included from include/linux/module.h:22,
>                     from include/linux/device/driver.h:21,
>                     from include/linux/device.h:32,
>                     from include/linux/iio/iio.h:10,
>                     from include/linux/iio/buffer.h:10,
>                     from drivers/iio/imu/adis16550.c:12:
> >> drivers/iio/imu/adis16550.c:1202:18: error: expected ',' or ';' before 'IIO_ADISLIB'  
>     1202 | MODULE_IMPORT_NS(IIO_ADISLIB);
>          |                  ^~~~~~~~~~~
>    include/linux/moduleparam.h:26:61: note: in definition of macro '__MODULE_INFO'
>       26 |                 = __MODULE_INFO_PREFIX __stringify(tag) "=" info
>          |                                                             ^~~~
>    include/linux/module.h:299:33: note: in expansion of macro 'MODULE_INFO'
>      299 | #define MODULE_IMPORT_NS(ns)    MODULE_INFO(import_ns, ns)
>          |                                 ^~~~~~~~~~~
>    drivers/iio/imu/adis16550.c:1202:1: note: in expansion of macro 'MODULE_IMPORT_NS'
>     1202 | MODULE_IMPORT_NS(IIO_ADISLIB);
>          | ^~~~~~~~~~~~~~~~
> 
> 
> vim +1202 drivers/iio/imu/adis16550.c
> 
>   1196	
>   1197	MODULE_AUTHOR("Nuno Sa <nuno.sa@analog.com>");
>   1198	MODULE_AUTHOR("Ramona Gradinariu <ramona.gradinariu@analog.com>");
>   1199	MODULE_AUTHOR("Antoniu Miclaus <antoniu.miclaus@analog.com>");
>   1200	MODULE_DESCRIPTION("Analog Devices ADIS16550 IMU driver");
>   1201	MODULE_LICENSE("GPL");
> > 1202	MODULE_IMPORT_NS(IIO_ADISLIB);  
> 

You need a base commit from rc2 or above.  (technically 2 patches after rc1
but rc2 is probably a better choice!)  This will be material for next kernel
release anyway now so this all may become moot!

Jonathan

  reply	other threads:[~2025-01-12 15:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  7:42 [PATCH v4 0/6] Add support for ADIS16550 and ADIS16550W Robert Budai
2025-01-10  7:42 ` [PATCH v4 1/6] iio: imu: adis: Add custom ops struct Robert Budai
2025-01-10  7:42 ` [PATCH v4 2/6] iio: imu: adis: Add reset to custom ops Robert Budai
2025-01-12 15:35   ` Jonathan Cameron
2025-01-10  7:42 ` [PATCH v4 3/6] iio: imu: adis: Add DIAG_STAT register size Robert Budai
2025-01-12 15:39   ` Jonathan Cameron
2025-01-10  7:42 ` [PATCH v4 4/6] dt-bindings: iio: Add adis16550 bindings Robert Budai
2025-01-12 15:48   ` Jonathan Cameron
2025-01-13  9:29     ` Nuno Sá
2025-01-13 14:22       ` Budai, Robert
2025-01-14  8:19         ` Nuno Sá
2025-01-13  8:43   ` Krzysztof Kozlowski
2025-01-15 13:35     ` Budai, Robert
2025-01-10  7:42 ` [PATCH v4 5/6] iio: imu: adis16550: add adis16550 support Robert Budai
2025-01-11 12:03   ` kernel test robot
2025-01-12 15:33     ` Jonathan Cameron [this message]
2025-01-12  4:20   ` kernel test robot
2025-01-12 16:11   ` Jonathan Cameron
2025-01-13  9:36     ` Nuno Sá
2025-01-13  9:48     ` Nuno Sá
2025-01-10  7:42 ` [PATCH v4 6/6] docs: iio: add documentation for adis16550 driver Robert Budai

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=20250112153358.16631b46@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=lanzano.alex@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=nuno.sa@analog.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ramona.gradinariu@analog.com \
    --cc=robert.budai@analog.com \
    --cc=robh@kernel.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 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).