From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.20]) (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 2853C25B09D for ; Wed, 13 May 2026 21:03:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.20 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778706214; cv=none; b=sVA3iXGYevg8S4XyS/bZHvkUILbaeJR5r/27mIDiuAKuP8ZkZb2c6ZQNLWFcdJjN0pUKEzMDGN3k1LUm87lpT+cID7tuslBGN+dj2FbfP4fZ9mkFYjhjEp6+PPRnpxNFhgNXkPTg+OIwDssfdySdjECF8NPWdeaSR70oAdKl8Rg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778706214; c=relaxed/simple; bh=wIrcCt65tv+2Ewy8fUYbWMcrfKw4vfCGjxAcLp6NdJs=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=sUvXneUF8RM7VfAgoVFSOMu7Uqe0vpRKx/IsOzGzDt8GEto1PVzoLnhYyne9obFIp91k2W+QMo6OTeBQSzqV4sbDN0XhuEJZe2jVbiKcjqBiGSEnG5MlOBT9vmxPpDG3UxplUkgogQfJuUdmMBNX4dilOGcVTimqEcr4zmLIg8c= 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=Dz1s1XxZ; arc=none smtp.client-ip=198.175.65.20 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="Dz1s1XxZ" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1778706213; x=1810242213; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=wIrcCt65tv+2Ewy8fUYbWMcrfKw4vfCGjxAcLp6NdJs=; b=Dz1s1XxZSivpFBbHk02qzautxr6Oej7Kx4wcAmZR10n6BuSBzHGt2E0b VHRwsJ0B6kj2463Pp03nRAzKYaEXor9r6iIFQvmIjWYy3fHB4SWIDSrEl rKGxwHbbFE+YvtF9E7EY/d8DMt2PqfUuo97AkUmaYicDUhCg00YY+mNWX A+EuxtnHiDUxw3Pd3XAE95V+kmdJoJVXZdjDb09hhfrlpfwJYDdgSReQ3 mvvpBhYbWuyvDnbxbZjvzIGBMtN0npQq6ZOPMC0lF8JND+rixAMjcUc/W VN5ExsS6AG+Ta+Z5Yaxma/4tFxmVRKecIzH0SWh8F0QVbw3B4LfflED/n g==; X-CSE-ConnectionGUID: 9mW4VKkXT5yAsnzELWopfw== X-CSE-MsgGUID: W9F40pwDQ5Od8Cm6yGP/rA== X-IronPort-AV: E=McAfee;i="6800,10657,11785"; a="79359753" X-IronPort-AV: E=Sophos;i="6.23,233,1770624000"; d="scan'208";a="79359753" Received: from orviesa006.jf.intel.com ([10.64.159.146]) by orvoesa112.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 May 2026 14:03:32 -0700 X-CSE-ConnectionGUID: XZM/lHqEQMuPRWPYTRUW4g== X-CSE-MsgGUID: LEq9y/i2QtCRvM4PVXDnuA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,233,1770624000"; d="scan'208";a="237215767" Received: from slindbla-desk.ger.corp.intel.com (HELO localhost) ([10.245.244.106]) by orviesa006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 May 2026 14:03:32 -0700 Date: Thu, 14 May 2026 00:03:28 +0300 From: Andy Shevchenko To: Andrew Jones Cc: linux-kernel@vger.kernel.org, apw@canonical.com, joe@perches.com, dwaipayanray1@gmail.com, lukas.bulwahn@gmail.com Subject: Re: [PATCH] checkpatch: warn on uppercase N/Y/M as Kconfig tristate literals Message-ID: References: <20260513205745.636737-1-andrew.jones@linux.dev> 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: <20260513205745.636737-1-andrew.jones@linux.dev> Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Wed, May 13, 2026 at 03:57:45PM -0500, Andrew Jones wrote: > Kconfig tristate literals are always lowercase ('n', 'y', 'm') and > uppercase N/Y/M are not Kconfig reserved words. Since undefined > symbols evaluate to 'n', writing 'default Y' or 'default M' silently > produces 'n' instead of 'y'/'m'. 'default N' happens to produce the > right value but is still invalid syntax. > > Add a warning for N/Y/M in Kconfig expressions found by following > the same preprocessing logic used by the Kconfig parser itself. > > This new warning was inspired by work done for [1]. Acked-by: Andy Shevchenko -- With Best Regards, Andy Shevchenko