public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	linux-kernel@vger.kernel.org, speakup@linux-speakup.org
Subject: Re: [PATCHv2] speakup: Generate speakupmap.h automatically
Date: Mon, 9 May 2022 16:04:43 +0200	[thread overview]
Message-ID: <YnkfeyobcOOgDGkH@kroah.com> (raw)
In-Reply-To: <20220430073321.6b4lvrrt7buzh7dp@begin>

On Sat, Apr 30, 2022 at 09:33:21AM +0200, Samuel Thibault wrote:
> speakupmap.h was not actually intended to be source code, speakupmap.map
> is.
> 
> This resurrects the makemapdata.c and genmap.c tools to generate
> speakupmap.h automatically from the input and speakup headers, and the
> speakupmap.map keyboard mapping source file.
> 
> Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> 
> ---
> difference with v1:
> - Add missing dependency between main.c and speakupmap.h
> 
>  drivers/accessibility/speakup/Makefile      |   28 ++++
>  drivers/accessibility/speakup/genmap.c      |  162 ++++++++++++++++++++++++++++
>  drivers/accessibility/speakup/makemapdata.c |  125 +++++++++++++++++++++
>  drivers/accessibility/speakup/speakupmap.h  |   66 -----------
>  drivers/accessibility/speakup/utils.c       |   92 +++++++++++++++
>  drivers/accessibility/speakup/utils.h       |   33 +++++
>  6 files changed, 440 insertions(+), 66 deletions(-)

Any reason you can't add the code in utils.c into genmap.c and then
merge into makemapdata.c to make this a single .c file that does both
things?

And when this is applied, I get the following "extra" files in the tree
that need to be properly ignored, so I couldn't take this as-is anyway:

❯ git status
On branch work-testing
Untracked files:
  (use "git add <file>..." to include in what will be committed)
	drivers/accessibility/speakup/genmap
	drivers/accessibility/speakup/makemapdata
	drivers/accessibility/speakup/mapdata.h
	drivers/accessibility/speakup/speakupmap.h

nothing added to commit but untracked files present (use "git add" to track)

thanks,

greg k-h

  reply	other threads:[~2022-05-09 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30  0:39 [PATCH] speakup: Generate speakupmap.h automatically Samuel Thibault
2022-04-30  7:33 ` [PATCHv2] " Samuel Thibault
2022-05-09 14:04   ` Greg KH [this message]
2022-05-09 14:07     ` Samuel Thibault
2022-05-09 14:19       ` Greg KH
2022-05-09 14:26         ` Samuel Thibault
2022-05-09 16:28           ` Greg KH
2022-05-09 16:36             ` Samuel Thibault
2022-05-15 23:03   ` [PATCHv3] " Samuel Thibault

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=YnkfeyobcOOgDGkH@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=speakup@linux-speakup.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