From: John Levon <levon@movementarian.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: smatch@vger.kernel.org, Dan Carpenter <dan.carpenter@oracle.com>
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: Sun, 25 Nov 2018 23:29:14 +0000 [thread overview]
Message-ID: <20181125232914.GA29607@movementarian.org> (raw)
In-Reply-To: <20181125212955.6kz3tsf735yrekug@ltop.local>
On Sun, Nov 25, 2018 at 10:29:56PM +0100, Luc Van Oostenryck wrote:
> This is copied from existing patches from sparse:
> https://git.kernel.org/pub/scm/devel/sparse/sparse.git/commit/?id=2f922ba822da324ccd2c201c076ca94d5e910a8a
> https://git.kernel.org/pub/scm/devel/sparse/sparse.git/commit/?id=d32b2f7c202fd27206169ca99da898ca9c20dfab
Hi Luc, apologies. I did in fact mention this patch was in part from
upstream.
> without giving credit and without respecting the Signed-off-by /
> Developer Certificate of Origin (cfr. https://developercertificate.org/).
I'm not clear how this isn't covered under part b) here.
Please clarify exactly what you would like me to do.
regards
john
next prev parent reply other threads:[~2018-11-26 10:21 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 [this message]
2018-11-26 0:27 ` Luc Van Oostenryck
2018-11-26 7:49 ` Dan Carpenter
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=20181125232914.GA29607@movementarian.org \
--to=levon@movementarian.org \
--cc=dan.carpenter@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox