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=-8.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no 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 8853EC3A59D for ; Tue, 20 Aug 2019 21:26:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5B9DB206DD for ; Tue, 20 Aug 2019 21:26:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="YezYmx2W" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730680AbfHTV0o (ORCPT ); Tue, 20 Aug 2019 17:26:44 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:36293 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730273AbfHTV0o (ORCPT ); Tue, 20 Aug 2019 17:26:44 -0400 Received: by mail-pg1-f195.google.com with SMTP id l21so43033pgm.3 for ; Tue, 20 Aug 2019 14:26:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kfF4vdGcFJm/Wf6JQ1wcuplxthXZW1HNbOa1JyPqpZg=; b=YezYmx2WChZMi1DRr1XoN8XfZITumH+PgqY3JQdS5w4u2vwKLbtcH66ah2vjoQnnog QyUxcFY+vLpiQeDhK9KTH5U7uOLNo0vnuD4a52N1MJjkiOZI294BDWFVvwrEEKdhPBaO XVT2+i53gVsOodGBAl0E+xI0gCcD/lVNo3bqvB93NFaE/xG/irV6qGiYAx5Sa0TgkhIz Derb91GymDQKbZ5lMgnZKtNSZMjrGXdFpCsjUGQOYWWslojKah3JT/incq30S9xuCblQ rssihHZxJUKUKjpEGuvFLm+OHFk0eFFOuKdMDTyPyJe4rypnj3lPr/tiL1vR+LS2dnzq EaFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kfF4vdGcFJm/Wf6JQ1wcuplxthXZW1HNbOa1JyPqpZg=; b=IffguUkFZEgAX029Up0hZA56U/ZYULahzHBTpZouu+eEeOkKWfAmw3V/YkfgQupGjm Dh2Nsb6w+qjCES8evY8N1TKmxXcSy1kUZxWs4Nan7iQtB9ir+qTjLiGjP+Y3EF5uzKmz YeIh+PEjc1rTZyySiKpMDCirJ3dTvd8W75n7b67f7jcvZm3Q5eeMQSud7jqNkKBuiW6R 4apaa5r5NbKOiK1YN/1rxsvplJVFc3DiHulGf7RRyKql5RByDz4Fq6jHYJLm0k4btoqd dERvoOREwKvndZnYktQD2aILtl4OVhx4GOobjXXxlJWAyzoNTqnj3ER+ogHFaAudoEIo yQ4w== X-Gm-Message-State: APjAAAWSnqe65GoZLa1TT1PZDM3YpQDP+rYs6BBeA6pk97vuXBldgYcC Crw2Gb2j1A197INu2o775Frl7tDZnLr6ZTbSIAxBgg== X-Google-Smtp-Source: APXvYqzLsasEUUNlQqQQsMBDlcH+Tp5YqnFlWE8k2udTHXgEapZH91qiWX0NVeTeH8163H7ZgTGtPG9Wj/vODuCC5PA= X-Received: by 2002:aa7:8f2e:: with SMTP id y14mr32322000pfr.113.1566336403144; Tue, 20 Aug 2019 14:26:43 -0700 (PDT) MIME-Version: 1.0 References: <20190814055108.214253-1-brendanhiggins@google.com> <5b880f49-0213-1a6e-9c9f-153e6ab91eeb@kernel.org> <20190820182450.GA38078@google.com> In-Reply-To: From: Brendan Higgins Date: Tue, 20 Aug 2019 14:26:32 -0700 Message-ID: Subject: Re: [PATCH v13 00/18] kunit: introduce KUnit, the Linux kernel unit testing framework To: shuah Cc: Frank Rowand , Greg KH , Josh Poimboeuf , Kees Cook , Kieran Bingham , Luis Chamberlain , Peter Zijlstra , Rob Herring , Stephen Boyd , "Theodore Ts'o" , Masahiro Yamada , devicetree , dri-devel , kunit-dev@googlegroups.com, "open list:DOCUMENTATION" , linux-fsdevel@vger.kernel.org, linux-kbuild , Linux Kernel Mailing List , "open list:KERNEL SELFTEST FRAMEWORK" , linux-nvdimm , linux-um@lists.infradead.org, Sasha Levin , "Bird, Timothy" , Amir Goldstein , Dan Carpenter , Daniel Vetter , Jeff Dike , Joel Stanley , Julia Lawall , Kevin Hilman , Knut Omang , Logan Gunthorpe , Michael Ellerman , Petr Mladek , Randy Dunlap , Richard Weinberger , David Rientjes , Steven Rostedt , wfg@linux.intel.com, Bjorn Helgaas Content-Type: text/plain; charset="UTF-8" Sender: linux-kselftest-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org On Tue, Aug 20, 2019 at 12:08 PM shuah wrote: > > On 8/20/19 12:24 PM, Brendan Higgins wrote: > > On Tue, Aug 20, 2019 at 11:24:45AM -0600, shuah wrote: > >> On 8/13/19 11:50 PM, Brendan Higgins wrote: > >>> ## TL;DR > >>> > >>> This revision addresses comments from Stephen and Bjorn Helgaas. Most > >>> changes are pretty minor stuff that doesn't affect the API in anyway. > >>> One significant change, however, is that I added support for freeing > >>> kunit_resource managed resources before the test case is finished via > >>> kunit_resource_destroy(). Additionally, Bjorn pointed out that I broke > >>> KUnit on certain configurations (like the default one for x86, whoops). > >>> > >>> Based on Stephen's feedback on the previous change, I think we are > >>> pretty close. I am not expecting any significant changes from here on > >>> out. > >>> > >> > >> Hi Brendan, > >> > >> I found checkpatch errors in one or two patches. Can you fix those and > >> send v14. > > > > Hi Shuah, > > > > Are you refering to the following errors? > > > > ERROR: Macros with complex values should be enclosed in parentheses > > #144: FILE: include/kunit/test.h:456: > > +#define KUNIT_BINARY_CLASS \ > > + kunit_binary_assert, KUNIT_INIT_BINARY_ASSERT_STRUCT > > > > ERROR: Macros with complex values should be enclosed in parentheses > > #146: FILE: include/kunit/test.h:458: > > +#define KUNIT_BINARY_PTR_CLASS \ > > + kunit_binary_ptr_assert, KUNIT_INIT_BINARY_PTR_ASSERT_STRUCT > > > > These values should *not* be in parentheses. I am guessing checkpatch is > > getting confused and thinks that these are complex expressions, when > > they are not. > > > > I ignored the errors since I figured checkpatch was complaining > > erroneously. > > > > I could refactor the code to remove these macros entirely, but I think > > the code is cleaner with them. > > > > Please do. I am not veru sure what value these macros add. Alright, I will have something for you later today.