From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.13]) (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 65C84219300; Mon, 24 Feb 2025 12:28:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.13 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740400124; cv=none; b=mzY+zfjc18uOwXFLRi1SC9RzriiFgruRQYbXhAEVlQBhxNo0h2nWho/wITL4MRyPuoQLXTYe/LwrPu2CkLTv5FHZOhPRFKkr8Hel6AyLH/fkaWuUwAp0n4W382tbkWYcGrh+guuLj42wpmH5bUgD5l7CgAmCxjIXCiHIj1ZZvLI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740400124; c=relaxed/simple; bh=HY86v1D01B8de8bRnCwQfhrLaS7Uve8orhJi2zLc/AQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=jh4LUgKKlM4Edd4PJWrIeokMDdiu+/UXo2MJHe8N4+t+m1WDc4DwdeSdERNuEl5DjqzLAhP81KaCwMcEXRSY8flUDxrmdbApLyi28Y/qcH7n4EaVROUH2hh51y1wsTemIU3mBrBwvrZhzD1xQdWs5cR7ZtgwrgXT66JYDkwWN8w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=none smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=oGfXPRpo; arc=none smtp.client-ip=198.175.65.13 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="oGfXPRpo" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1740400124; x=1771936124; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=HY86v1D01B8de8bRnCwQfhrLaS7Uve8orhJi2zLc/AQ=; b=oGfXPRpoazB8Nz67eKcV+7uYQok9c9CXZp+D7vLhxuepnCgePkPabIUK w9hDhHHZ0YA9dNLxueXxUoGd4iRFwmL5oAb/8S54kWhF7ozwPKO1fBsGG 6vvMzP8UTVjdyPL/+eVBzSC6rnIGV+A9oRf8Tru1dLIgrtPRLPL/0zfdn 5jblIw67GGj6e+mFBVMOSgBP+RGMCf8ydUm1BXLx6e+uBS1My8qLhY66s ScASDymsf8Tvk2aIpFuRJ0LAgMiWihe2Wk/Hx7nD4TpJdsfhcxg0qvukR tERcSe+bZoasfYsywGAGN1G7UxHU3LSMUN8e8ZT3TYIXrvEOn6y2bu2yo Q==; X-CSE-ConnectionGUID: ssKEkSpoS6yv019XEUxxsg== X-CSE-MsgGUID: BC6RzgrcS0i/cFAftZZZ+A== X-IronPort-AV: E=McAfee;i="6700,10204,11355"; a="52143192" X-IronPort-AV: E=Sophos;i="6.13,309,1732608000"; d="scan'208";a="52143192" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by orvoesa105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Feb 2025 04:28:43 -0800 X-CSE-ConnectionGUID: 5iuv9pjeSqGU3LIzJDbdHQ== X-CSE-MsgGUID: oR1SJYDNStqf2Ekl4VOMnQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.12,224,1728975600"; d="scan'208";a="116532987" Received: from smile.fi.intel.com ([10.237.72.58]) by orviesa007.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Feb 2025 04:28:39 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.98) (envelope-from ) id 1tmXZb-0000000Eh02-268V; Mon, 24 Feb 2025 14:28:35 +0200 Date: Mon, 24 Feb 2025 14:28:35 +0200 From: Andy Shevchenko To: Raag Jadav Cc: kernel test robot , perex@perex.cz, tiwai@suse.com, broonie@kernel.org, lgirdwood@gmail.com, deller@gmx.de, sre@kernel.org, sakari.ailus@linux.intel.com, mchehab@kernel.org, hverkuil-cisco@xs4all.nl, jdmason@kudzu.us, fancer.lancer@gmail.com, oe-kbuild-all@lists.linux.dev, linux-sound@vger.kernel.org, linux-fbdev@vger.kernel.org, linux-pm@vger.kernel.org, linux-media@vger.kernel.org, ntb@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 07/13] fbdev: pxafb: use devm_kmemdup_array() Message-ID: References: <20250221165333.2780888-8-raag.jadav@intel.com> <202502220449.DvJuMgsL-lkp@intel.com> Precedence: bulk X-Mailing-List: ntb@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: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo On Mon, Feb 24, 2025 at 02:22:07PM +0200, Raag Jadav wrote: > On Mon, Feb 24, 2025 at 01:41:05PM +0200, Andy Shevchenko wrote: > > On Mon, Feb 24, 2025 at 01:24:08PM +0200, Raag Jadav wrote: > > > On Mon, Feb 24, 2025 at 12:58:35PM +0200, Andy Shevchenko wrote: > > > > On Sat, Feb 22, 2025 at 05:41:24AM +0800, kernel test robot wrote: > > > > > Hi Raag, > > > > > > > > > > kernel test robot noticed the following build warnings: > > > > > > > > > > [auto build test WARNING on b16e9f8547a328b19af59afc213ce323124d11e9] > > > > > > > > > > url: https://github.com/intel-lab-lkp/linux/commits/Raag-Jadav/ASoC-Intel-avs-use-devm_kmemdup_array/20250222-010322 > > > > > base: b16e9f8547a328b19af59afc213ce323124d11e9 > > > > > patch link: https://lore.kernel.org/r/20250221165333.2780888-8-raag.jadav%40intel.com > > > > > patch subject: [PATCH v1 07/13] fbdev: pxafb: use devm_kmemdup_array() > > > > > config: arm-randconfig-004-20250222 (https://download.01.org/0day-ci/archive/20250222/202502220449.DvJuMgsL-lkp@intel.com/config) > > > > > compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0 > > > > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250222/202502220449.DvJuMgsL-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/202502220449.DvJuMgsL-lkp@intel.com/ > > > > > > > > > > All warnings (new ones prefixed by >>): > > > > > > > > > > drivers/video/fbdev/pxafb.c: In function 'pxafb_probe': > > > > > >> drivers/video/fbdev/pxafb.c:2236:13: warning: unused variable 'i' [-Wunused-variable] > > > > > 2236 | int i, irq, ret; > > > > > | ^ > > > > > > > > Ragg, please, fix this, and issue a v2 with the link to fixed PR: > > > > https://lore.kernel.org/r/Z7xGpz3Q4Zj6YHx7@black.fi.intel.com. > > > > > > Sure, but perhaps wait a few days for review comments. > > > > Then perhaps answering to the cover letter that the maintainers who want to > > apply should use the updated PR? > > Okay, but I'm not sure how this plays out for those who already pulled > the old PR, i.e. Sebastian. > > Anything to worry about here? I already informed him and Stephen about a new PR I just sent a few hours ago. -- With Best Regards, Andy Shevchenko