[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1432159260-39390-1-git-send-email-olof@lixom.net>
Date: Wed, 20 May 2015 15:00:50 -0700
From: Olof Johansson <olof@...om.net>
To: yann.morin.1998@...e.fr
Cc: linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
dvhart@...ux.intel.com, john.stultz@...aro.org, jwboyer@...hat.com
Subject:
>From Olof Johansson <olof@...om.net> # This line is ignored.
From: Olof Johansson <olof@...om.net>
Subject: [PATCH 00/10] merge_config.sh: Misc reworks
In-Reply-To:
Hi,
Somewhat wide distribution list here, since I've added everyone who's
touched the script, with the presumption that those have been the major
users of it. Please make sure none of these changes break your usecases.
I've done some reworks of merge_config.sh. I was quite hesitant to start
this since there are no good ways to see if your changes break others
or not, so the first thing I did was to add some tests. I know this is
highly unorthodox so try not to panic.
As far as what this series does is:
- Adds a way to pass in CONFIG_FOO=<value> on the command line, it gets
treated as a single-entry fragment
- The script now prints the warnings on stderr, and returns non-0 when
something is encountered
- Optionally, it'll also return non-0 when a redundant entry is found. I
presumed people rely on -r not being a failure so I did this separately
- CONFIG_FOO=n and "# CONFIG_FOO is not set" is now treated the same,
and using the former doesn't cause an invalid warning when the results
are checked at the end
- Slightly odd things happened if a fragment contains the same option
twice: It'd produce a warning that was malformed. Now just ignore that
and use only the latest value of said option.
-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists