From: kernel test robot <lkp@intel.com>
To: "David Lechner" <dlechner@baylibre.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Eugen Hristev" <eugen.hristev@linaro.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>
Cc: oe-kbuild-all@lists.linux.dev, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/6] iio: introduce IIO_DECLARE_BUFFER_WITH_TS macros
Date: Thu, 24 Apr 2025 01:25:08 +0800 [thread overview]
Message-ID: <202504240112.hZy9LpvD-lkp@intel.com> (raw)
In-Reply-To: <20250422-iio-introduce-iio_declare_buffer_with_ts-v2-1-3fd36475c706@baylibre.com>
Hi David,
kernel test robot noticed the following build errors:
[auto build test ERROR on aff301f37e220970c2f301b5c65a8bfedf52058e]
url: https://github.com/intel-lab-lkp/linux/commits/David-Lechner/iio-introduce-IIO_DECLARE_BUFFER_WITH_TS-macros/20250423-061049
base: aff301f37e220970c2f301b5c65a8bfedf52058e
patch link: https://lore.kernel.org/r/20250422-iio-introduce-iio_declare_buffer_with_ts-v2-1-3fd36475c706%40baylibre.com
patch subject: [PATCH v2 1/6] iio: introduce IIO_DECLARE_BUFFER_WITH_TS macros
config: sh-randconfig-001-20250424 (https://download.01.org/0day-ci/archive/20250424/202504240112.hZy9LpvD-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250424/202504240112.hZy9LpvD-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/202504240112.hZy9LpvD-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/iio/industrialio-buffer.c:29:
>> include/linux/iio/iio.h:813:1: error: static assertion failed: "macros above assume that IIO_DMA_MINALIGN also ensures s64 timestamp alignment"
813 | _Static_assert(sizeof(IIO_DMA_MINALIGN) % sizeof(s64) == 0,
| ^~~~~~~~~~~~~~
vim +813 include/linux/iio/iio.h
781
782 #define _IIO_DECLARE_BUFFER_WITH_TS(type, name, count) \
783 type name[ALIGN((count), sizeof(s64) / sizeof(type)) + sizeof(s64) / sizeof(type)]
784
785 /**
786 * IIO_DECLARE_BUFFER_WITH_TS() - Declare a buffer with timestamp
787 * @type: element type of the buffer
788 * @name: identifier name of the buffer
789 * @count: number of elements in the buffer
790 *
791 * Declares a buffer that is safe to use with iio_push_to_buffer_with_ts(). In
792 * addition to allocating enough space for @count elements of @type, it also
793 * allocates space for a s64 timestamp at the end of the buffer and ensures
794 * proper alignment of the timestamp.
795 */
796 #define IIO_DECLARE_BUFFER_WITH_TS(type, name, count) \
797 _IIO_DECLARE_BUFFER_WITH_TS(type, name, count) __aligned(sizeof(s64))
798
799 /**
800 * IIO_DECLARE_DMA_BUFFER_WITH_TS() - Declare a DMA-aligned buffer with timestamp
801 * @type: element type of the buffer
802 * @name: identifier name of the buffer
803 * @count: number of elements in the buffer
804 *
805 * Same as IIO_DECLARE_BUFFER_WITH_TS(), but is uses __aligned(IIO_DMA_MINALIGN)
806 * to ensure that the buffer doesn't share cachelines with anything that comes
807 * before it in a struct. This should not be used for stack-allocated buffers
808 * as stack memory cannot generally be used for DMA.
809 */
810 #define IIO_DECLARE_DMA_BUFFER_WITH_TS(type, name, count) \
811 _IIO_DECLARE_BUFFER_WITH_TS(type, name, count) __aligned(IIO_DMA_MINALIGN)
812
> 813 _Static_assert(sizeof(IIO_DMA_MINALIGN) % sizeof(s64) == 0,
814 "macros above assume that IIO_DMA_MINALIGN also ensures s64 timestamp alignment");
815
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-23 17:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 22:07 [PATCH v2 0/6] iio: introduce IIO_DECLARE_BUFFER_WITH_TS David Lechner
2025-04-22 22:07 ` [PATCH v2 1/6] iio: introduce IIO_DECLARE_BUFFER_WITH_TS macros David Lechner
2025-04-22 22:30 ` Andy Shevchenko
2025-04-22 22:37 ` David Lechner
2025-04-22 22:50 ` Andy Shevchenko
2025-04-23 9:18 ` Nuno Sá
2025-04-23 14:51 ` David Lechner
2025-04-23 15:43 ` Andy Shevchenko
2025-04-24 7:44 ` Nuno Sá
2025-04-26 11:19 ` Jonathan Cameron
2025-04-23 17:25 ` kernel test robot [this message]
2025-04-23 17:46 ` kernel test robot
2025-04-22 22:07 ` [PATCH v2 2/6] iio: adc: ad4695: use u16 for buffer elements David Lechner
2025-04-22 22:07 ` [PATCH v2 3/6] iio: adc: ad4695: use IIO_DECLARE_BUFFER_WITH_TS David Lechner
2025-04-22 22:34 ` Andy Shevchenko
2025-04-22 22:07 ` [PATCH v2 4/6] iio: adc: ad7380: " David Lechner
2025-04-22 22:33 ` Andy Shevchenko
2025-04-22 22:41 ` David Lechner
2025-04-22 22:53 ` Andy Shevchenko
2025-04-22 22:07 ` [PATCH v2 5/6] iio: accel: sca3300: " David Lechner
2025-04-22 22:07 ` [PATCH v2 6/6] iio: adc: at91-sama5d2: " David Lechner
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=202504240112.hZy9LpvD-lkp@intel.com \
--to=lkp@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andy@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=dlechner@baylibre.com \
--cc=eugen.hristev@linaro.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=nuno.sa@analog.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