From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1FD24C04A6B for ; Wed, 8 May 2019 06:25:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EFCDF21019 for ; Wed, 8 May 2019 06:25:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726644AbfEHGZz (ORCPT ); Wed, 8 May 2019 02:25:55 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:45083 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726082AbfEHGZz (ORCPT ); Wed, 8 May 2019 02:25:55 -0400 Received: from p5de0b374.dip0.t-ipconnect.de ([93.224.179.116] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hOG1Y-0002Ba-Ri; Wed, 08 May 2019 08:25:53 +0200 Date: Wed, 8 May 2019 08:25:51 +0200 (CEST) From: Thomas Gleixner To: Greg KH cc: linux-spdx@vger.kernel.org Subject: Re: [patch 0/4] SPDX: First batch of patches In-Reply-To: <20190507185816.GC17205@kroah.com> Message-ID: References: <20190507121952.495564307@linutronix.de> <20190507141746.GA28384@kroah.com> <20190507181435.GB13061@kroah.com> <20190507185816.GC17205@kroah.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org Greg, On Tue, 7 May 2019, Greg KH wrote: > > Anyway, glad to help out if you want me to. Running the scripts is one thing. The more important thing is to figure out how we are going to review these patches and agree that the conclusion is correct. Ideally we have lots of Reviewed-by's on each of them. Yes, it's 500+ and some of them are really large, but the point is that at least in my opinion it's enough to carefully review the 'normalized' patterns which are in the change log. I have some postprocessing checks (not yet in utils) which verify that author/copyright notices which are in the middle of the removed crap are preserved. The other issue which I worked on yesterday night (krobot finding a few corner cases where the patcher did not handle some odd comment formatting correctly) should be gone. I just started a new full run to verify that. Apropos changelog. You said they need some care. If you check out the utils repo, there are templates in the step2/3 directories and the subdirectories of step1. If you could work on them that would be appreciated. Thanks, tglx