From: Dan Carpenter <dan.carpenter@oracle.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: John Levon <levon@movementarian.org>, smatch@vger.kernel.org
Subject: Re: [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
Date: Mon, 26 Nov 2018 10:49:09 +0300 [thread overview]
Message-ID: <20181126074909.GI2970@unbuntlaptop> (raw)
In-Reply-To: <20181126002734.rmk5kmvtjtol2m2h@ltop.local>
It looks like everything was BCC instead of To: and Cc:? I can't tell
which went to linux-sparse and which smatch@vger.kernel.org. Smatch is
GPL and Sparse is MIT, but any shared code is MIT licensed.
I would like to sync with upstream Sparse, but I tried a couple months
back and it got complicated so I have procrastinated. But I could just
cherry-pick those two patches. Or John, you could cherry-pick them and
send them to me. `man git cherry-pick`.
regards,
dan carpenter
next prev parent reply other threads:[~2018-11-26 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 12:08 [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason John Levon
2018-11-25 21:29 ` Luc Van Oostenryck
2018-11-25 23:29 ` John Levon
2018-11-26 0:27 ` Luc Van Oostenryck
2018-11-26 7:49 ` Dan Carpenter [this message]
2018-11-29 10:03 ` Sync smatch with sparse? Luc Van Oostenryck
2018-11-29 10:09 ` John Levon
2018-11-26 8:44 ` [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason John Levon
2018-11-26 9:18 ` Dan Carpenter
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=20181126074909.GI2970@unbuntlaptop \
--to=dan.carpenter@oracle.com \
--cc=levon@movementarian.org \
--cc=luc.vanoostenryck@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.