From: Bastien Nocera <hadess@hadess.net>
To: Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 1/2] keytable: Add source information in generated keymaps
Date: Thu, 04 Jul 2019 15:22:48 +0200 [thread overview]
Message-ID: <e83329c72c8a29eb8e1164292663284e818a649f.camel@hadess.net> (raw)
In-Reply-To: <20190703153317.yuv4wxp52w3ingmx@gofer.mess.org>
On Wed, 2019-07-03 at 16:33 +0100, Sean Young wrote:
> On Mon, Jul 01, 2019 at 06:38:12PM +0200, Bastien Nocera wrote:
> > Add comments to mention that keymap files are generated, and that
> > they shouldn't be modified by hand. Also list which tool was used
> > to generate them and the kernel source filename.
> >
> > Signed-off-by: Bastien Nocera <hadess@hadess.net>
> > ---
> > utils/keytable/gen_keytables.pl | 9 ++++++++-
> > 1 file changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/utils/keytable/gen_keytables.pl
> > b/utils/keytable/gen_keytables.pl
> > index 4124e366..3dc74ba6 100755
> > --- a/utils/keytable/gen_keytables.pl
> > +++ b/utils/keytable/gen_keytables.pl
> > @@ -36,10 +36,17 @@ 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 "# This file is a generated data file, do not modify
> > manually\n";
> > + print OUT "#\n";
> > + print OUT "# Generated with gen_keytables.pl in v4l-utils\n";
> > + print OUT "# using $relative_filename as a source file\n";
>
> This is only relevant for a developer who is wanting to upstream
> their
> keymap changes to v4l-utils.
It's only relevant to you. Or the chump that tried to do things well
(me). I wouldn't have wasted this much time writing tests, or making
patches if there had been a bit of guidance on how you wanted those
problems fixed. I'll let you create a README for that instead.
I'll send the "check" patch again.
prev parent reply other threads:[~2019-07-04 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 16:38 [PATCH 1/2] keytable: Add source information in generated keymaps Bastien Nocera
2019-07-01 16:38 ` [PATCH 2/2] keytable: Remove comments before processing keymaps Bastien Nocera
2019-07-02 9:08 ` Sean Young
2019-07-02 9:29 ` Bastien Nocera
2019-07-02 9:43 ` Bastien Nocera
2019-07-02 11:44 ` Sean Young
2019-07-02 13:20 ` Bastien Nocera
2019-07-03 15:33 ` [PATCH 1/2] keytable: Add source information in generated keymaps Sean Young
2019-07-04 13:22 ` Bastien Nocera [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e83329c72c8a29eb8e1164292663284e818a649f.camel@hadess.net \
--to=hadess@hadess.net \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).