From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C01B123F27B for ; Mon, 30 Jun 2025 09:56:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.10 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751277400; cv=none; b=X9bQRm3brzB0BlrJ/TKt3HPJ4WizLBYUnsF6Sv4/flQXgMGW15OL0oPWdoSXxrfGxLV5WKWdPKwryuReVJARKZPh4mDWhdJADsvPuu5vWIZDPR/vyR1/4zTjxJGw3gQgvFb4dpFRuRrgT379zmtbCxUVPXuNJ4q2l5bal5CddEw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751277400; c=relaxed/simple; bh=lRurOeZ7EKZfBhd+PazQpT0UPsCtzFmVV3p9ECRTaxo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=VL9Qg8SqUjCIArWOSG4iihJf+9mBqkdkYfNxVt9UTXkDRqSserGQC5WxhwxtLwbjx7Kb2scAF21ezOkXEC4TBVpgIWk6eSZ99ccOvObaaYcCDuhKLxD7bKKt59WU1QRNsBxnZztCQf1zlfV1RPXYtSeopVnfM0tf8695rq/V2dQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=CzRWn/r2; arc=none smtp.client-ip=198.175.65.10 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="CzRWn/r2" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1751277398; x=1782813398; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=lRurOeZ7EKZfBhd+PazQpT0UPsCtzFmVV3p9ECRTaxo=; b=CzRWn/r2TjTMKm3l5tUKR3fGibva3aUl92K0crjh4Uo94Hs0tMrR1EMy 2kb2kXiHpWgUCLz0xjHid1dEAe+Tm0ZAqN+86+zjJy/bJmxNotfSmGPJm aBCcNfCaL+iA1NCVKoCyjplU7gix2Gnvx30vXKzfbWquykqqgjKRwOSEI Fe3weER7mSTbDB+oO7fopUCJDdU+B8VAfFf8rD3r73QFzZHFGo1leGEW6 nkygTG1D1Y6hT6hOGIKgtJsbunF50aEj94bww/XDUf1N1mUyEenHtDB+H hsTW3M6SIbLVDSmVpN9I8zYRORa9m28+8E2AgMXxtj/cLLiIDedChnYZq A==; X-CSE-ConnectionGUID: FVAleGTHTh+d9epK9H4JPQ== X-CSE-MsgGUID: l/EAMGN7T0Oow+UxdQ3ICA== X-IronPort-AV: E=McAfee;i="6800,10657,11479"; a="70932089" X-IronPort-AV: E=Sophos;i="6.16,277,1744095600"; d="scan'208";a="70932089" Received: from fmviesa007.fm.intel.com ([10.60.135.147]) by orvoesa102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Jun 2025 02:56:38 -0700 X-CSE-ConnectionGUID: dNZuO+IMSw25ZROr0r/Png== X-CSE-MsgGUID: Slrx0BFzS4G/O/KiCbWXHQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,277,1744095600"; d="scan'208";a="153044245" Received: from lkp-server01.sh.intel.com (HELO e8142ee1dce2) ([10.239.97.150]) by fmviesa007.fm.intel.com with ESMTP; 30 Jun 2025 02:56:35 -0700 Received: from kbuild by e8142ee1dce2 with local (Exim 4.96) (envelope-from ) id 1uWBFY-000Yks-2G; Mon, 30 Jun 2025 09:56:32 +0000 Date: Mon, 30 Jun 2025 17:56:00 +0800 From: kernel test robot To: Dave Airlie , dri-devel@lists.freedesktop.org, linux-mm@kvack.org, Johannes Weiner , Christian Koenig Cc: oe-kbuild-all@lists.linux.dev, Dave Chinner , Kairui Song , Dave Airlie Subject: Re: [PATCH 10/17] ttm: add a memcg accounting flag to the alloc/populate APIs Message-ID: <202506301731.dRh8GUQZ-lkp@intel.com> References: <20250630045005.1337339-11-airlied@gmail.com> Precedence: bulk X-Mailing-List: oe-kbuild-all@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250630045005.1337339-11-airlied@gmail.com> Hi Dave, kernel test robot noticed the following build warnings: [auto build test WARNING on drm/drm-next] [cannot apply to akpm-mm/mm-everything linus/master v6.16-rc4 next-20250630] [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/Dave-Airlie/drm-ttm-use-gpu-mm-stats-to-track-gpu-memory-allocations-v2/20250630-134938 base: git://anongit.freedesktop.org/drm/drm drm-next patch link: https://lore.kernel.org/r/20250630045005.1337339-11-airlied%40gmail.com patch subject: [PATCH 10/17] ttm: add a memcg accounting flag to the alloc/populate APIs config: riscv-randconfig-001-20250630 (https://download.01.org/0day-ci/archive/20250630/202506301731.dRh8GUQZ-lkp@intel.com/config) compiler: riscv64-linux-gcc (GCC) 8.5.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250630/202506301731.dRh8GUQZ-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 | Closes: https://lore.kernel.org/oe-kbuild-all/202506301731.dRh8GUQZ-lkp@intel.com/ All warnings (new ones prefixed by >>): >> Warning: drivers/gpu/drm/ttm/ttm_bo.c:1256 function parameter 'memcg_account' not described in 'ttm_bo_populate' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki