From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.9]) (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 00E8138E8BE; Tue, 7 Jul 2026 09:02:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.9 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783414956; cv=none; b=Uq7f6qJ/i55vBuMccAxZHf8WteAff7FEtkA4zZWZI2llLmLnKb8DeQJ1VCbBtEEvZDZgVtuWFT+JOl9YxgxFf+86YJrjmlv8WkMxSu2cWmmK010C9pEO2SceUVh+FsC6tbeYW37TEHyNhrYk2ZckAghqILQwrLZfqMXZUHtgjhM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783414956; c=relaxed/simple; bh=+e+ez9ewvt0ECIJbO/nKkoaBW6MIulXZo8Sc0cbiZro=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=U3pP9IvR4L9kK+rI60ocOBapgTL7MvGp+kbmeZqP53Udd4jLkAV0eq1gLuZ9bTMr40qt5B8DWDDNp2LzZrj+JgpyUcPYSR6jyVWYdb0YTkgeoDMrW9de+bsSaZW1IC13zfsrm2C7vHfCKVj1qBjKATWfF7Sl+aUTpAArqV5QTJs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=aSVIX2y8; arc=none smtp.client-ip=192.198.163.9 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass 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="aSVIX2y8" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1783414954; x=1814950954; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=+e+ez9ewvt0ECIJbO/nKkoaBW6MIulXZo8Sc0cbiZro=; b=aSVIX2y82vo8zUehaNLOFqJZMoO9vBnkE+eNn7QOTqaUtyz04SoP7+uS 0RTgQI0ioH6VqeXP23mIgXnhmyRMMBLmarJhYTCxhhaoQ2n8/75Szn09K sIB541Pkep+ctcSUxA7QkJNXFC2+wOKaTWrzDsfSrF7yk/k4TmkK68NXm D/YV0jOpVc2EIVGGIJIiSBUIPOHDOZPEMIrq50CNlIYV+3wGO0+/GBwLi Fa0e0/02s2z3Uf4318VHzc4jxt+QMkV1TMsiZNja4r8i1ZK9SkY/OeVce 344VctyS2sjGOybhGMK5Pu66GRFEZgRGNS84LMa+aZqquA1ztBtNL4sV3 A==; X-CSE-ConnectionGUID: c1lhTsPCTm62uOstoLfd8Q== X-CSE-MsgGUID: 0+cw6w5vSvGcuY7DohtSLA== X-IronPort-AV: E=McAfee;i="6800,10657,11839"; a="94702511" X-IronPort-AV: E=Sophos;i="6.25,153,1779174000"; d="scan'208";a="94702511" Received: from orviesa010.jf.intel.com ([10.64.159.150]) by fmvoesa103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jul 2026 02:02:33 -0700 X-CSE-ConnectionGUID: hZsRr+XZRJuF1HByaaTvcA== X-CSE-MsgGUID: VTWvL/QdTue5Ae6n9N3UMQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.25,153,1779174000"; d="scan'208";a="252871119" Received: from abityuts-desk.ger.corp.intel.com (HELO localhost) ([10.245.244.178]) by orviesa010-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jul 2026 02:02:31 -0700 Date: Tue, 7 Jul 2026 12:02:28 +0300 From: Andy Shevchenko To: Greg Kroah-Hartman Cc: "Usyskin, Alexander" , Arnd Bergmann , "Nilawar, Badal" , "linux-kernel@vger.kernel.org" , "Adin, Menachem" , "stable@vger.kernel.org" , lkp Subject: Re: [PATCH char-misc v2] mei: lb: fix incorrect type in assignment Message-ID: References: <20260706-fix_type_le-v2-1-586826351454@intel.com> <2026070608-reformat-pungent-aeb4@gregkh> <2026070722-zips-outgrow-ee43@gregkh> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2026070722-zips-outgrow-ee43@gregkh> Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Tue, Jul 07, 2026 at 10:47:42AM +0200, Greg Kroah-Hartman wrote: > On Tue, Jul 07, 2026 at 10:21:42AM +0300, Andy Shevchenko wrote: > > On Tue, Jul 07, 2026 at 06:43:20AM +0000, Usyskin, Alexander wrote: > > > > On Mon, Jul 06, 2026 at 04:01:30PM +0300, Alexander Usyskin wrote: ... > > > > > Cc: stable@vger.kernel.org > > > > > > > > Why cc: stable? It doesn't actually cause any functional change to the > > > > code at all, right? This isn't running on s390, or am I mistaken? > > > > > > This driver is for discrete graphics card, so it may run on non-x86 system, thus all conversions. > > > > > > I've been told that if there is Fixes: for commit that already in stable, I should cc: stable. > > > If it is not hard rule, I'll drop cc: from the next patch revision. > > > > Cc'ing stable@ is a rule which is documented in-tree. Many developers just omit > > it for unknown reasons. > > My point is that this is NOT an actual bugfix that needs to be applied > anywhere except during the next merge window, as all it does is make > sparse quiet (which is a valid change). It doesn't do anything "real" > as this hardware is not on any big-endian systems. I was not objecting that. My comment was regarding to "if it's not a hard rule". > Please don't send stuff to stable that does not actually need to be in a > stable kernel tree. Fully agree. -- With Best Regards, Andy Shevchenko