From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.11]) (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 7FDFB4418D6 for ; Tue, 20 Jan 2026 20:50:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768942258; cv=none; b=TuyEw742ag/grfLdWEWWtMN6k+avVB0oaFY6dFhDZR2uxSoUbrdcuK/dD/OwPpehUij/fS2rmQJjJGe4MEqijXblhHFBkMJ7GrfEgpjqC4XJlOH4AK2YGCk2mz3gzltw18P9Tmxwenm0jxNCGhdsbGHVnk4HeTNC/VFyHo5gj90= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768942258; c=relaxed/simple; bh=uQtvY+Irsii/7hUOEy8iqRE/qOfIN+XGmkISMd2fW+0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=NtU8nUffh+njUyr2JbeUhj/jbfHMGxdpgPJBxFlgOaxR0CDERwdJ/bHd4WNcBqeVPc3tGC5vLtfl18FkYhazJQPeZdh2h1rJMiC9el1X9BTU1JXj1B/Wm4c0MvmDSwKgFtwtZC4cs5REY3Cb72QGT68OUN3mYZaIGxUJUEoAUU4= 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=Kz89cYAE; arc=none smtp.client-ip=198.175.65.11 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="Kz89cYAE" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1768942256; x=1800478256; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=uQtvY+Irsii/7hUOEy8iqRE/qOfIN+XGmkISMd2fW+0=; b=Kz89cYAEJcx16nwRKd0TeyMlsIE5I3xuf/vipFfxes/omcMxYAIHJKjL uZ4J5Y+Xh1CtRmnKNp1SV51NKcMc7cASWuN6OnySEubrlm4265ViuP0Yd qez+fnaW8bgi2XE+Tu8ES38guW2EWOenmQ5HVvHAEH8bH4YOyWE4YT5Bk xdngUNnUL6DH7uP7q3rnhNrGXbBWpjevbr/wUrbkq3taVFUhD3ORRbUrO k/r2lu82EpAfIxCtUhYWaPOZmF7M6g5ZLf92Z2PniAwGDWvdOkz2L+dqF fekDMy+ADJKU8g77Mu+OM7Gcmu4kLC7U8PHM7/0yEx9gKTXIhvtz6Xavo A==; X-CSE-ConnectionGUID: sFDLM+5SSiWOFVZE3tH57Q== X-CSE-MsgGUID: kr8Gm2FsS5O+h5fG1dnZ0Q== X-IronPort-AV: E=McAfee;i="6800,10657,11677"; a="80467858" X-IronPort-AV: E=Sophos;i="6.21,241,1763452800"; d="scan'208";a="80467858" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by orvoesa103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Jan 2026 12:50:56 -0800 X-CSE-ConnectionGUID: 6HM7WGlpSHSzfeYRlOEVNA== X-CSE-MsgGUID: qxKv8ADDRJqpUL5uNkkjfA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,241,1763452800"; d="scan'208";a="206279306" Received: from black.igk.intel.com ([10.91.253.5]) by orviesa007.jf.intel.com with ESMTP; 20 Jan 2026 12:50:54 -0800 Received: by black.igk.intel.com (Postfix, from userid 1003) id 4C2EE95; Tue, 20 Jan 2026 21:50:52 +0100 (CET) Date: Tue, 20 Jan 2026 21:50:52 +0100 From: "Shevchenko, Andriy" To: "Luck, Tony" Cc: Dave Hansen , "linux-kernel@vger.kernel.org" , "Mehta, Sohil" , Borislav Petkov , "H. Peter Anvin" , Ingo Molnar , "Kohler, Jon" , Pawan Gupta , "Peter Zijlstra (Intel)" , Thomas Gleixner , "x86@kernel.org" Subject: Re: [PATCH 1/6] x86/cpu: Break Vendor/Family/Model macros into separate header Message-ID: References: <20260119195047.86E3C696@davehans-spike.ostc.intel.com> <20260119195049.43DDFD4E@davehans-spike.ostc.intel.com> 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: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo On Tue, Jan 20, 2026 at 04:48:55PM +0000, Luck, Tony wrote: > > > Signed-off-by: Dave Hansen > > > > Still don't understand why people putting Cc list before the cutter. This noise > > in the commit message and when retrospectively one reads on the small screen (I > > do on the phone from time to time) it makes it at bare miniumum inconvenient). > > > > > Cc: Thomas Gleixner > > > Cc: Ingo Molnar > > > Cc: Borislav Petkov > > > Cc: Dave Hansen > > > Cc: "H. Peter Anvin" > > > Cc: Tony Luck > > > Cc: Pawan Gupta > > > Cc: "Peter Zijlstra (Intel)" > > > Cc: x86@kernel.org > > > Cc: Jon Kohler > > > --- > > I put stuff above the "---" because I'm a dinosaur using GIT and often use: > > $ git format-patch .... > > ... > > $ git am 00* I couldn't imagine why I would need to use this flow for my own changes. We have rebase, worktree, multiple remotes in one tree, etc. I think the keyword is 'dinosaur' and now is 21st century :-) > to rebase, reorder, move bits from one patch to another, or generate a new > version of the series. When I do so the "git am" drops everything after the "---" cut line. > > I poked around, but couldn't find any way to make "git am" keep it :-( That's the idea, to get them dropped when a maintainer applies the series. lore.kernel.org will keep the list anyway. Haven't researched `b4 relay`, maybe that one helps to carry the Cc list on... -- With Best Regards, Andy Shevchenko