public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Wolfram Sang <wsa-dev@sang-engineering.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	oe-kbuild-all@lists.linux.dev,
	Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: [PATCH v2 2/6] i2c: core: Unify the firmware node type check
Date: Mon, 7 Apr 2025 16:48:37 +0300	[thread overview]
Message-ID: <Z_PXtXIUi4VRjICJ@smile.fi.intel.com> (raw)
In-Reply-To: <202504072041.Bv9mOk4o-lkp@intel.com>

On Mon, Apr 07, 2025 at 08:45:14PM +0800, kernel test robot wrote:
> Hi Andy,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on wsa/i2c/for-next]
> [also build test ERROR on linus/master v6.15-rc1 next-20250407]
> [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/Andy-Shevchenko/i2c-core-Drop-duplicate-check-before-calling-OF-APIs/20250407-180528
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
> patch link:    https://lore.kernel.org/r/20250407095852.215809-3-andriy.shevchenko%40linux.intel.com
> patch subject: [PATCH v2 2/6] i2c: core: Unify the firmware node type check
> config: arc-randconfig-002-20250407 (https://download.01.org/0day-ci/archive/20250407/202504072041.Bv9mOk4o-lkp@intel.com/config)
> compiler: arc-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250407/202504072041.Bv9mOk4o-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/202504072041.Bv9mOk4o-lkp@intel.com/
> 

> All error/warnings (new ones prefixed by >>):

Ah, I should compile-test the slave part as well...
Will be fixed in v3. Since v3 is required, Tomi, I'm going to add the media
patch to its end.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-04-07 13:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  9:55 [PATCH v2 0/6] i2c: core: Move client towards fwnode Andy Shevchenko
2025-04-07  9:55 ` [PATCH v2 1/6] i2c: core: Drop duplicate check before calling OF APIs Andy Shevchenko
2025-04-07  9:55 ` [PATCH v2 2/6] i2c: core: Unify the firmware node type check Andy Shevchenko
2025-04-07 12:45   ` kernel test robot
2025-04-07 13:48     ` Andy Shevchenko [this message]
2025-04-07 13:47   ` kernel test robot
2025-04-07  9:55 ` [PATCH v2 3/6] i2c: core: Switch to fwnode APIs to get IRQ Andy Shevchenko
2025-04-07 13:47   ` kernel test robot
2025-04-07  9:55 ` [PATCH v2 4/6] i2c: core: Reuse fwnode variable where it makes sense Andy Shevchenko
2025-04-07  9:55 ` [PATCH v2 5/6] i2c: core: Do not dereference fwnode in struct device Andy Shevchenko
2025-04-07  9:55 ` [PATCH v2 6/6] i2c: core: Deprecate of_node in struct i2c_board_info Andy Shevchenko
2025-04-07 11:34 ` [PATCH v2 0/6] i2c: core: Move client towards fwnode Tomi Valkeinen
2025-04-07 12:23   ` Andy Shevchenko

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=Z_PXtXIUi4VRjICJ@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=wsa-dev@sang-engineering.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