Powered by Linux
Re: [PATCH 2/2] smatch: fix typos — Semantic Matching Tool

Re: [PATCH 2/2] smatch: fix typos

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 17, 2024 at 06:48:35PM +0300, Andrew Kreimer wrote:
> Fix typos in documentation, comments, etc.
> 
> Via codespell.
> 
> Signed-off-by: Andrew Kreimer <algonell@xxxxxxxxx>
> ---
>  README                  |  2 +-
>  cgcc                    |  2 +-
>  check_host_input.c      | 12 ++++++------
>  check_preempt.c         |  2 +-
>  cse.c                   |  4 ++--
>  cwchash/hashtable.c     |  2 +-
>  evaluate.c              |  4 ++--
>  expand.c                |  2 +-
>  flow.c                  |  4 ++--
>  lib.c                   |  2 +-
>  linearize.c             |  2 +-
>  opcode.def              |  2 +-
>  pre-process.c           |  4 ++--
>  simplify.c              |  4 ++--
>  unssa.c                 |  2 +-
>  utils.h                 |  2 +-
>  validation/bool-array.c |  2 +-
>  17 files changed, 27 insertions(+), 27 deletions(-)

Thanks, Andrew.

I've merged patch 1 but it's a tricky thing to merge patch 2.  Most of these
files come from Sparse and not Smatch.  Smatch files basically start with
smatch_, check_ or validation/sm_.  So these changes should be sent to
linux-sparse@xxxxxxxxxxxxxxx.  There are two problems with me merging this:

1) The license for Sparse is MIT and the license for Smatch is GPLv2+.  Merging
   spelling fixes doesn't really count in terms of copyrights, but I don't
   want to deal with that.  I'd prefer if it we not mix code with different
   licenses and the Sparse code was sent to the Sparse list.

2) When I merge updated code from Sparse it causes conflicts because they will
   have the wrong spellings and I'll have to fix it up by hand.

regards,
dan carpenter





[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux