From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from movementarian.org ([178.79.150.28]:52050 "EHLO movementarian.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726027AbeKZKVb (ORCPT ); Mon, 26 Nov 2018 05:21:31 -0500 Date: Sun, 25 Nov 2018 23:29:14 +0000 From: John Levon 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. Message-ID: <20181125232914.GA29607@movementarian.org> References: <20181125212955.6kz3tsf735yrekug@ltop.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181125212955.6kz3tsf735yrekug@ltop.local> Sender: smatch-owner@vger.kernel.org List-ID: To: Luc Van Oostenryck Cc: smatch@vger.kernel.org, Dan Carpenter 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