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=-2.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 D3F60C43215 for ; Sat, 23 Nov 2019 23:50:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A962620674 for ; Sat, 23 Nov 2019 23:50:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="ASgrvDPj" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726880AbfKWXuB (ORCPT ); Sat, 23 Nov 2019 18:50:01 -0500 Received: from mail-il1-f195.google.com ([209.85.166.195]:45992 "EHLO mail-il1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726759AbfKWXuB (ORCPT ); Sat, 23 Nov 2019 18:50:01 -0500 Received: by mail-il1-f195.google.com with SMTP id o18so10778267ils.12 for ; Sat, 23 Nov 2019 15:50:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=s4GCLK+fIVn+snaTOmwkPoaXDJP7z3FcdVJMD3d4BQk=; b=ASgrvDPj4A/sFmDffZ+2PUQ5GRVEw02fOaSJyhpnDMyd/H5wMQMT7uoyC6CSBOV0DN XshcS1H7NEePIkGvTrLcYM+wJjDXbAY0UALDwOCzKe9eJJU2jp9LBkFJhwqKmQOc06om /3RULDjh5ysrs72RSWCed9tWmL1qV0D0ATRvna9IgeYdj/JxvGbuoJ3mgWWyy4nKgXdT WhRqjru2yEpjEVtQ5VAZiiiN+bjb9NczEH4SKT4u3F8HbVLB29jNhQSDi06IE3ISaQCc Or9q/yVZqf9WmSQ9q71QDzHPdCJ1AlOw1Mra3SKkK84m0+qD88loZLVykWYE/aGiE5dG Z/CQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=s4GCLK+fIVn+snaTOmwkPoaXDJP7z3FcdVJMD3d4BQk=; b=htqfRiJ2Kb7xmy8gKdEqIVhs6tBZOBxzXk+mbixnkaUHbugJRfGde+UD8uKDucUZIa D1Zwlx1R1SMx47yFwmV/dlWHAqKUJcMw4ILDeRA4jYb1v6B5cVhhlOci9jJ52gO2x32o QQfx+4df7Fs8kjpPFrKr7XCI8MUd+umj4i4cnk69YyltXy47VMTaVif9Hf+6LH96tqwn JnNSkym5gD+FG6mYgqO45HYyxufP0FEZ/tXH8ThMLgrfd46O9zRIul5hOVF6WCd1DO1j v7JaXySIZKWqumI5wpFk8KjawIZy9qaa89/GieWWi5BaUu+/B94CUjc1bou2LZIvRcQS FQEw== X-Gm-Message-State: APjAAAVaaf2yRRGskg00HRUTSSBJOP2eBLA72ep+Gm7E0zb/B+cMMPST y615IyYFbX4S6ABx6ikViZsc7A== X-Google-Smtp-Source: APXvYqwfIV3uzdikoiQkcpfkAzGQuZULk1koZ3M8WX2S/VzCwOcD7E1RvKXMwMxHjNC5GYXTXUVh1Q== X-Received: by 2002:a92:680e:: with SMTP id d14mr26576786ilc.224.1574553000174; Sat, 23 Nov 2019 15:50:00 -0800 (PST) Received: from localhost ([64.62.168.194]) by smtp.gmail.com with ESMTPSA id g12sm596204ion.82.2019.11.23.15.49.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 23 Nov 2019 15:49:59 -0800 (PST) Date: Sat, 23 Nov 2019 15:49:56 -0800 (PST) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Dan Williams cc: Jonathan Corbet , linux-riscv@lists.infradead.org, palmer@dabbelt.com, aou@eecs.berkeley.edu, krste@berkeley.edu, waterman@eecs.berkeley.edu, Linux Kernel Mailing List , Linux Doc Mailing List Subject: Re: [PATCH] Documentation: riscv: add patch acceptance guidelines In-Reply-To: Message-ID: References: <20191123092552.1438bc95@lwn.net> User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 23 Nov 2019, Dan Williams wrote: > On Sat, Nov 23, 2019 at 3:27 PM Paul Walmsley wrote: > > > It looks like the main thing that would be needed would be to add the P: > > entry with the path to our patch-acceptance.rst file into the MAINTAINERS > > file, after Dan's patches are merged. > > > > Of course, we could also add more information about sparse cleanliness, > > checkpatch warnings, etc., but we mostly try to follow the common kernel > > guidelines there. > > Those could likely be automated to highlight warnings that a given > subsystem treats as errors, but wherever possible my expectation is > that the policy should be specified globally. > > > Is that summary accurate, or did I miss some additional steps? > > I'll go fixup and get the into patch submitted today then we can go from > there. I guess I'm still looking for guidance along the lines of my earlier question: what (if anything) would we need to change about the current patch to have it work with the maintainer profile documentation (beyond the "P:" entry in MAINTAINERS) ? - Paul