public inbox for smatch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Kreimer <algonell@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: smatch@vger.kernel.org
Subject: Re: [PATCH 2/2] smatch: fix typos
Date: Fri, 18 Oct 2024 12:50:18 +0300	[thread overview]
Message-ID: <ZxIvWs0oBpdNcwIm@void.void> (raw)
In-Reply-To: <835cb1d2-3531-4607-a85e-08202fae33aa@stanley.mountain>

On Thu, Oct 17, 2024 at 10:25:39PM +0300, Dan Carpenter wrote:
> 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@vger.kernel.org.  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
> 

Understood, thank you!

      reply	other threads:[~2024-10-18  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 15:48 [PATCH 0/2] Fix typos Andrew Kreimer
2024-10-17 15:48 ` [PATCH 1/2] smatch: fix typos Andrew Kreimer
2024-10-17 15:48 ` [PATCH 2/2] " Andrew Kreimer
2024-10-17 19:25   ` Dan Carpenter
2024-10-18  9:50     ` Andrew Kreimer [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=ZxIvWs0oBpdNcwIm@void.void \
    --to=algonell@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=smatch@vger.kernel.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