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.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_PASS,USER_AGENT_MUTT 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 A7CDEECDE3D for ; Sat, 20 Oct 2018 13:51:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 63B652152F for ; Sat, 20 Oct 2018 13:51:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="cUfSHsFr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 63B652152F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727693AbeJTWCa (ORCPT ); Sat, 20 Oct 2018 18:02:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:59636 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727364AbeJTWC3 (ORCPT ); Sat, 20 Oct 2018 18:02:29 -0400 Received: from localhost (10.193.71.37.rev.sfr.net [37.71.193.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9D659214C3; Sat, 20 Oct 2018 13:51:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1540043516; bh=c66SbdJE2DGgHUPROthSQlNoEQXhg0tTvTvyMmUWTXg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cUfSHsFrfL82xX2ygU7oKkknXukvuf3jlQaE5JF6PVb+QxAfDCo7tlJHp5D2wUNel VQQXTUX+BGGrH9n3JXHftJrZoe0wHAZKysx3JqZWGt3y4xAZpu5pKGrOAedh9ix1u4 HtT1XBzXcuCKE8F8EToPgcokYcXlpMOTi1boIulQ= Date: Sat, 20 Oct 2018 15:49:32 +0200 From: Greg Kroah-Hartman To: linux-kernel Cc: ksummit-discuss@lists.linuxfoundation.org, Thomas Gleixner , Olof Johansson , Chris Mason , Mishi Choudhary Subject: [PATCH 1/7] Code of conduct: Fix wording around maintainers enforcing the code of conduct Message-ID: <20181020134932.GB32218@kroah.com> References: <20181020134908.GA32218@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20181020134908.GA32218@kroah.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Chris Mason As it was originally worded, this paragraph requires maintainers to enforce the code of conduct, or face potential repercussions. It sends the wrong message, when really we just want maintainers to be part of the solution and not violate the code of conduct themselves. Removing it doesn't limit our ability to enforce the code of conduct, and we can still encourage maintainers to help maintain high standards for the level of discourse in their subsystem. Signed-off-by: Chris Mason Acked-by: Alex Deucher Acked-by: Amir Goldstein Acked-by: Andrew Morton Acked-by: Ard Biesheuvel Acked-by: Benjamin Herrenschmidt Acked-by: Boris Brezillon Acked-by: Borislav Petkov Acked-by: Christian Lütke-Stetzkamp Acked-by: Christoph Hellwig Acked-by: Colin Ian King Acked-by: Dan Carpenter Acked-by: Dan Williams Acked-by: Daniel Borkmann Acked-by: Dave Airlie Acked-by: Dave Hansen Acked-by: David Ahern Acked-by: David Sterba Acked-by: Dmitry Torokhov Acked-by: Eric Dumazet Acked-by: Felipe Balbi Acked-by: Felix Kuehling Acked-by: Florian Fainelli Acked-by: Florian Westphal Acked-by: Geert Uytterhoeven Acked-by: Gregory CLEMENT Acked-by: Guenter Roeck Acked-by: Gustavo A. R. Silva Acked-by: Hans Verkuil Acked-by: Hans de Goede Acked-by: Harry Wentland Acked-by: Heiko Stuebner Acked-by: Ingo Molnar Acked-by: Jaegeuk Kim Acked-by: James Smart Acked-by: James Smart Acked-by: Jan Kara Acked-by: Jason A. Donenfeld Acked-by: Jeff Kirsher Acked-by: Jens Axboe Acked-by: Jessica Yu Acked-by: Jia-Ju Bai Acked-by: Jiri Kosina Acked-by: Jiri Olsa Acked-by: Joerg Roedel Acked-by: Johan Hovold Acked-by: Johannes Thumshirn Acked-by: Jonathan Corbet Acked-by: Julia Lawall Acked-by: Kees Cook Acked-by: Kirill Tkhai Acked-by: Kuninori Morimoto Acked-by: Laurent Pinchart Acked-by: Lina Iyer Acked-by: Linus Torvalds Acked-by: Linus Walleij Acked-by: Mark Brown Acked-by: Masahiro Yamada Acked-by: Masami Hiramatsu Acked-by: Matias Bjørling Acked-by: Maxime Ripard Acked-by: Michael Ellerman Acked-by: Mimi Zohar Acked-by: Miquel Raynal Acked-by: Nikolay Borisov Acked-by: Oded Gabbay Acked-by: Olof Johansson Acked-by: Palmer Dabbelt Acked-by: Paul E. McKenney Acked-by: Peter Zijlstra Acked-by: Rafael J. Wysocki Acked-by: Richard Weinberger Acked-by: Rik van Riel Acked-by: Rob Clark Acked-by: Rob Herring Acked-by: Rodrigo Vivi Acked-by: Sebastian Andrzej Siewior Acked-by: Sebastian Reichel Acked-by: Sergio Paracuellos Acked-by: Shawn Guo Acked-by: Shuah Khan Acked-by: Simon Horman Acked-by: Srinivas Kandagatla Acked-by: Stephen Hemminger Acked-by: Takashi Iwai Acked-by: Tejun Heo Acked-by: Theodore Ts'o Acked-by: Thierry Reding Acked-by: Thomas Gleixner Acked-by: Tim Bird Acked-by: Todd Poynor Acked-by: Wei Yongjun Acked-by: YueHaibing Reviewed-by: Mauro Carvalho Chehab Reviewed-by: Steven Rostedt Signed-off-by: Greg Kroah-Hartman --- Documentation/process/code-of-conduct.rst | 4 ---- 1 file changed, 4 deletions(-) diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst index ab7c24b5478c..a2641c19cf26 100644 --- a/Documentation/process/code-of-conduct.rst +++ b/Documentation/process/code-of-conduct.rst @@ -70,10 +70,6 @@ appropriate to the circumstances. The TAB is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. -Maintainers who do not follow or enforce the Code of Conduct in good faith may -face temporary or permanent repercussions as determined by other members of the -project’s leadership. - Attribution =========== -- 2.19.1