aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBastien Nocera <hadess@hadess.net>2021-01-26 18:45:14 +0100
committerSean Young <sean@mess.org>2021-03-06 15:28:53 +0000
commit786b776ae95916f352ab1745c5d55f0eaa21cdd4 (patch)
tree11bfc110b804f61de2ba4480421c5965491f34c7
parentdb8039584d0112aeb520bb7f33181fc824e77ba8 (diff)
downloadv4l-utils-786b776ae95916f352ab1745c5d55f0eaa21cdd4.tar.gz
keytable: Add source information in generated keymaps
Add comments to mention that keymap files are generated, and list which tool was used to generate them and the kernel source filename. This should make it less likely that generated files are used as examples to contribute keymaps from, and more likely that upstream changes are channeled through the right source tree. Signed-off-by: Bastien Nocera <hadess@hadess.net> Signed-off-by: Sean Young <sean@mess.org>
-rwxr-xr-xutils/keytable/gen_keytables.pl6
1 files changed, 5 insertions, 1 deletions
diff --git a/utils/keytable/gen_keytables.pl b/utils/keytable/gen_keytables.pl
index c14aded3..32f9cfd4 100755
--- a/utils/keytable/gen_keytables.pl
+++ b/utils/keytable/gen_keytables.pl
@@ -36,10 +36,14 @@ sub flush($$)
my $filename = shift;
my $legacy = shift;
my $defined;
+ my $relative_filename = $filename;
return if (!$keyname || !$out);
- print "Creating $dir/$keyname.toml\n";
+ $relative_filename =~ s/^$kernel_dir//;
+ $relative_filename =~ s/^\///;
+ print "Creating $dir/$keyname.toml from $relative_filename\n";
open OUT, ">$dir/$keyname.toml";
+ print OUT "# Generated with gen_keytables.pl from $relative_filename\n";
print OUT "[[protocols]]\n";
print OUT "name = \"$keyname\"\n";
print OUT "protocol = \"$type\"\n";