Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751286AbbGLHmE (ORCPT ); Sun, 12 Jul 2015 03:42:04 -0400 Received: from faui40.informatik.uni-erlangen.de ([131.188.34.40]:34286 "EHLO faui40.informatik.uni-erlangen.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750948AbbGLHmD (ORCPT ); Sun, 12 Jul 2015 03:42:03 -0400 From: Andreas Ruprecht To: Ulf Magnusson Cc: Paul Bolle , Valentin Rothberg , rafael.j.wysocki@intel.com, , , hengelein Stefan , linux@dominikbrodowski.net, Michal Marek , Andreas Ruprecht Subject: [PATCH v4 0/2] kconfig: warn of unhandled characters in Kconfig commands Date: Sun, 12 Jul 2015 09:41:49 +0200 Message-Id: X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1368 Lines: 41 This patchset changes the lexer file to emit a warning if any unhandled characters are found in the input. So far, Kconfig options like +config FOO bool [...] (note the wrong '+'!) were parsed without a warning. As simply adding a warning for '.' produces lots of warnings as occasionally '---help---' is used instead of 'help' (and thus '-' is recognized as an unhandled character), we need to handle '---help---' separately. Changes to v1: - add '---help---' in zconf.gperf instead of special casing it in zconf.l Changes to v2: - Do no constify char parameter to warn_ignored_character - Shorten rule definitions for '.' Changes to v3: - spaces -> tabs in zconf.gperf Andreas Ruprecht (2): kconfig: warn of unhandled characters in Kconfig commands kconfig: Regenerate shipped zconf.{hash,lex}.c files scripts/kconfig/zconf.gperf | 1 + scripts/kconfig/zconf.hash.c_shipped | 58 ++++--- scripts/kconfig/zconf.l | 20 ++- scripts/kconfig/zconf.lex.c_shipped | 325 +++++++++++++++++------------------ 4 files changed, 204 insertions(+), 200 deletions(-) -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/