Received: by 2002:a05:7412:cfc7:b0:fc:a2b0:25d7 with SMTP id by7csp1171535rdb; Mon, 19 Feb 2024 06:36:42 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCW2N6jgDSVa4A6GVOo7Dg/p8UbKWA9z+0JFzByEnpxGS2026wN/DsHWVpLU6tOXPptgF1S1fNAqTHQIu1pnYhqHN3LbnHonvvvKGTzT4A== X-Google-Smtp-Source: AGHT+IFytp+9kp8gRBKk6GlkEYfR6OpVtBLy0IyXXkBnKpUYfhP3GsaOC8jHfArAK5EFFtOkJs2L X-Received: by 2002:a05:6830:1418:b0:6e4:453b:be7 with SMTP id v24-20020a056830141800b006e4453b0be7mr6003427otp.32.1708353402315; Mon, 19 Feb 2024 06:36:42 -0800 (PST) Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id v12-20020a05622a188c00b0042e1212ec3bsi2499669qtc.0.2024.02.19.06.36.42 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Feb 2024 06:36:42 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-71486-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@intel.com header.s=Intel header.b=FDgxyvZN; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-71486-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-71486-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id B64021C226F3 for ; Mon, 19 Feb 2024 14:35:51 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 6C48C36AF8; Mon, 19 Feb 2024 14:35:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=intel.com header.i=@intel.com header.b="FDgxyvZN" Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.14]) (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 19EC737155; Mon, 19 Feb 2024 14:35:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.14 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708353333; cv=none; b=ku2efWLu672s9k3z4rOPmTIheyLWz//vCmxUCBGv3whK2LEDJ8XoR+mBrZkUit4hw8TRQyX8ypp8UbtaDEyKgTljwAkMl/6/zLfCXR1KkOYz+EWifkf3078VWMFIYcLujednskfwu0dU3sO/3Th2XCgRcDCZhnMcxBGyvP75Dlw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708353333; c=relaxed/simple; bh=k2Lph/7vsIC7otT5TKfaEZcrEWoZc028leDXer26Ytc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=KoCHBhCXFU6jiyxB5ffX2ER8Uc6NDJWQ69VbvSKgBXh9jsWzWXr51NOixMhevKGrcOG8C+q0yzVKKeKid5BmIQnSkhbxQPV2riua34/hvhlWHaeOG86dUx9ePObU7nuMAGOXr05YOMmVuGGf2P3x0Dh+a5oqcdOdfErJCKOKzJ0= 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=FDgxyvZN; arc=none smtp.client-ip=192.198.163.14 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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1708353332; x=1739889332; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=k2Lph/7vsIC7otT5TKfaEZcrEWoZc028leDXer26Ytc=; b=FDgxyvZNbFo7oHyQ4Mso09FK2mwy7EmNzOHY88OdOnGUgHscgaCAo1ti wQWaaEh8S0J8+abfbUCiLNJqD4MB21Mq3pIdFeuVDLnL9moU2xmt0iyFA HPxajoOWh4yfeaHtnN4BJH/WQ3bl9O//LxTXLAftRsPxRLEJtkqv5SFMU lbLBys/K3LybtfD0YYHQ548JLwhQrd5JIQZKSqwJoq7U1oUgVz0iOwf81 AX87VHgCqrlvs43mVa72UfWzw56QDYSVR+DTKRV8WsBFbAy3B0ankwL80 HzCWNmNTGfx2xu6nMs1LY16HT/1u5HL/4KBfVqAdGQMQqrCAzuAYWsRK9 w==; X-IronPort-AV: E=McAfee;i="6600,9927,10988"; a="2580539" X-IronPort-AV: E=Sophos;i="6.06,170,1705392000"; d="scan'208";a="2580539" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmvoesa108.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Feb 2024 06:35:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10988"; a="827011627" X-IronPort-AV: E=Sophos;i="6.06,170,1705392000"; d="scan'208";a="827011627" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga001.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Feb 2024 06:35:27 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.97) (envelope-from ) id 1rc4jr-00000005qOC-2YNa; Mon, 19 Feb 2024 16:35:23 +0200 Date: Mon, 19 Feb 2024 16:35:23 +0200 From: Andy Shevchenko To: John Ogness Cc: Petr Mladek , Sergey Senozhatsky , Steven Rostedt , Thomas Gleixner , linux-kernel@vger.kernel.org, Greg Kroah-Hartman , Jiri Slaby , Ilpo =?iso-8859-1?Q?J=E4rvinen?= , Tony Lindgren , Geert Uytterhoeven , Justin Chen , Jiaqing Zhao , linux-serial@vger.kernel.org Subject: Re: [PATCH printk v2 08/26] printk: nbcon: Implement processing in port->lock wrapper Message-ID: References: <20240218185726.1994771-1-john.ogness@linutronix.de> <20240218185726.1994771-9-john.ogness@linutronix.de> <87jzn0bkqg.fsf@jogness.linutronix.de> 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: <87jzn0bkqg.fsf@jogness.linutronix.de> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo On Mon, Feb 19, 2024 at 03:24:47PM +0106, John Ogness wrote: > On 2024-02-19, Andy Shevchenko wrote: .. > >> #include > >> #include > >> #include > >> +#include > > > > The headers in this file is a mess. But here you can at least keep the > > piece ordered, can you? > > Just to clarify, you would like to see this ordering and inclusion? Roughly, yes. Ideally it is quite likely that kernel.h is being used as a 'proxy' header. Nowadays, it's rare the code needs kernel.h. > #include > #include > #include > #include > #include > #include > #include > #include -- With Best Regards, Andy Shevchenko