All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Lechner <dlechner@baylibre.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-staging@lists.linux.dev
Cc: oe-kbuild-all@lists.linux.dev,
	"David Lechner" <dlechner@baylibre.com>,
	linux-kernel@vger.kernel.org,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Axel Haslam" <ahaslam@baylibre.com>,
	"Philip Molloy" <pmolloy@baylibre.com>
Subject: Re: [PATCH 4/4] iio: resolver: add new driver for AD2S1210
Date: Thu, 21 Sep 2023 07:35:03 +0800	[thread overview]
Message-ID: <202309210740.YRdN185w-lkp@intel.com> (raw)
In-Reply-To: <20230920170253.203395-5-dlechner@baylibre.com>

Hi David,

kernel test robot noticed the following build warnings:

[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on linus/master v6.6-rc2 next-20230920]
[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/David-Lechner/dt-bindings-iio-resolver-add-devicetree-bindings-for-ad2s1210/20230921-010529
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link:    https://lore.kernel.org/r/20230920170253.203395-5-dlechner%40baylibre.com
patch subject: [PATCH 4/4] iio: resolver: add new driver for AD2S1210
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230921/202309210740.YRdN185w-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230921/202309210740.YRdN185w-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/202309210740.YRdN185w-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/iio/resolver/ad2s1210.c:113: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Writes the given data to the given register address.
   drivers/iio/resolver/ad2s1210.c:151: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Reads value from one of the registers.
   drivers/iio/resolver/ad2s1210.c:201: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Sets the excitation frequency and performs software reset.


vim +113 drivers/iio/resolver/ad2s1210.c

   111	
   112	/**
 > 113	 * Writes the given data to the given register address.
   114	 *
   115	 * If the mode is configurable, the device will first be placed in
   116	 * configuration mode.
   117	 */
   118	static int ad2s1210_regmap_reg_write(void *context, unsigned int reg,
   119					     unsigned int val)
   120	{
   121		struct ad2s1210_state *st = context;
   122		struct spi_transfer xfers[] = {
   123			{
   124				.len = 1,
   125				.rx_buf = &st->rx[0],
   126				.tx_buf = &st->tx[0],
   127				.cs_change = 1,
   128			}, {
   129				.len = 1,
   130				.rx_buf = &st->rx[1],
   131				.tx_buf = &st->tx[1],
   132			},
   133		};
   134		int ret;
   135	
   136		/* values can only be 7 bits, the MSB indicates an address */
   137		if (val & ~0x7F)
   138			return -EINVAL;
   139	
   140		st->tx[0] = reg;
   141		st->tx[1] = val;
   142	
   143		ret = ad2s1210_set_mode(st, AD2S1210_MODE_CONFIG);
   144		if (ret < 0)
   145			return ret;
   146	
   147		return spi_sync_transfer(st->sdev, xfers, ARRAY_SIZE(xfers));
   148	}
   149	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-09-20 23:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 17:02 [PATCH 0/4] iio: resolver: move ad2s1210 out of staging David Lechner
2023-09-20 17:02 ` [PATCH 1/4] dt-bindings: iio: resolver: add devicetree bindings for ad2s1210 David Lechner
2023-09-20 22:33   ` Rob Herring
2023-09-21  9:06   ` Conor Dooley
2023-09-21  9:40     ` David Lechner
2023-09-20 17:02 ` [PATCH 2/4] iio: sysfs: add IIO_DEVICE_ATTR_NAMED_RW macro David Lechner
2023-09-20 17:02 ` [PATCH 3/4] staging: iio: resolver: remove ad2s1210 driver David Lechner
2023-09-20 17:02 ` [PATCH 4/4] iio: resolver: add new driver for AD2S1210 David Lechner
2023-09-20 23:35   ` kernel test robot [this message]
2023-09-21 12:42   ` Jonathan Cameron
2023-09-21 15:45   ` Rob Herring
2023-09-22  7:54     ` 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=202309210740.YRdN185w-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=ahaslam@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=nuno.sa@analog.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pmolloy@baylibre.com \
    --cc=robh+dt@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 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.