From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55])
	(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 5EFAC18AEE
	for <linux-kernel@vger.kernel.org>; Fri, 15 Dec 2023 09:55:29 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="CtRHBobu";
	dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="qxBVBcMW"
Date: Fri, 15 Dec 2023 10:55:26 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de;
	s=2020; t=1702634128;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=pIxoKqnBpZE5IFm9QJMHfMhfAhKDM7qManzO753GghA=;
	b=CtRHBobuO9FREN0DTGa5eOpRxNp5OY6OE9NTDGxbOLBwX28m/V8PSOu3igwFkLbuq57iBi
	cFmp0lRJt9ZlLddkasAAVRJhIP71EBFsSNIkR82SjCQdRhZ5mO05viNg/2RgEWOS0vRo88
	i8BybdiZ84a1pPMg6EQG3hjLxC2MVxuCQrHTBB+dT/qN/jDK73ld7hHUwabJmzRNozXFPU
	6xyX4EOvexXxRgE+9U9mRrimhYgKOrIt+6fVfs4cUn8/7mtjX7MwBr0WcGYkC8fynadtSr
	BV9SuXg3lxtZAt31hbXRZNVn4I4p5XTSzdHK9YJSORAooVWNGXj8cUQF5js7xw==
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de;
	s=2020e; t=1702634128;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=pIxoKqnBpZE5IFm9QJMHfMhfAhKDM7qManzO753GghA=;
	b=qxBVBcMWO6Xx0Qn//Hn03sxmfnEAdal1fBjYAkoebl3ZNQzbGirCLUAVeGtV+nhtA7xXC4
	nhC7c99Oap3FzHDg==
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Ogness <john.ogness@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org,
	Francesco Dolcini <francesco@dolcini.it>,
	kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH printk v3 02/14] printk: Adjust mapping for 32bit seq
 macros
Message-ID: <20231215095526.ZA8Q-45e@linutronix.de>
References: <20231214214201.499426-1-john.ogness@linutronix.de>
 <20231214214201.499426-3-john.ogness@linutronix.de>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20231214214201.499426-3-john.ogness@linutronix.de>

On 2023-12-14 22:47:49 [+0106], John Ogness wrote:
> Note: This change only applies to 32bit architectures. On 64bit
>       architectures the macros are NOPs.

You lost my authorship.
But serious matter: Is this bug already present in the current printk
tree or is this code just not used and enabled later? Patch #1 from this
series moves the sequence around so is this problem introduced in the
previous patch and fixed here?

Sebastian