From patchwork Tue Apr 1 16:08:35 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Felipe Balbi X-Patchwork-Id: 27551 Return-Path: X-Original-To: linaro@patches.linaro.org Delivered-To: linaro@patches.linaro.org Received: from mail-pd0-f199.google.com (mail-pd0-f199.google.com [209.85.192.199]) by ip-10-151-82-157.ec2.internal (Postfix) with ESMTPS id 790FE20341 for ; Tue, 1 Apr 2014 16:11:08 +0000 (UTC) Received: by mail-pd0-f199.google.com with SMTP id x10sf24865011pdj.10 for ; Tue, 01 Apr 2014 09:11:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:delivered-to:from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:sender:precedence:list-id :x-original-sender:x-original-authentication-results:mailing-list :list-post:list-help:list-archive:list-unsubscribe:content-type; bh=XwuXuMbOJZrF7dFpgRAjNJTZ1j9grYjGNvYTMQEkqkg=; b=cokgvIvawzeJW8gbg8Eo4QaDTyKuJxEKaCKuuyxlnoyprAImoJ4RMI3anwegzVeoSj RL04248GeSZLrT9A5MB1kr92Hl/bIhS/MPLq3yEwzfh4HltqqIcMkqblatUhcVuqhe7k ZIPXP2VkbVhKNQGcdmzyiwQDQMpKkebL/f/GIN3mVXN9Ujj0SsDAhPlLjBKM2ArqXnH3 bv/9Q91JvSjmLkZDidySBqSB8bkFcxvQN9lPzDqFE5Krrp55TVhcfDCzch6r+lRqkNrO hyAZV6hdeOiDC5vLkC5pI7BKifvnuSEQUDZ3CbPE5VD4B7h5WigshSvZIDnb6AHRDzam pyKQ== X-Gm-Message-State: ALoCoQlZ/avwe9RiWHHFzoGYoaUUHMoKFjpQAyxrBbqN5cFxG5WM4ndtno5ssRS9q5sYZDQsUasY X-Received: by 10.66.66.109 with SMTP id e13mr13523045pat.1.1396368667701; Tue, 01 Apr 2014 09:11:07 -0700 (PDT) X-BeenThere: patchwork-forward@linaro.org Received: by 10.140.41.40 with SMTP id y37ls59870qgy.10.gmail; Tue, 01 Apr 2014 09:11:07 -0700 (PDT) X-Received: by 10.220.250.203 with SMTP id mp11mr28941955vcb.2.1396368667606; Tue, 01 Apr 2014 09:11:07 -0700 (PDT) Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by mx.google.com with ESMTPS id bj3si3738226vcb.64.2014.04.01.09.11.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Apr 2014 09:11:07 -0700 (PDT) Received-SPF: neutral (google.com: 209.85.220.176 is neither permitted nor denied by best guess record for domain of patch+caf_=patchwork-forward=linaro.org@linaro.org) client-ip=209.85.220.176; Received: by mail-vc0-f176.google.com with SMTP id lc6so9837786vcb.21 for ; Tue, 01 Apr 2014 09:11:07 -0700 (PDT) X-Received: by 10.220.159.4 with SMTP id h4mr29526114vcx.1.1396368667482; Tue, 01 Apr 2014 09:11:07 -0700 (PDT) X-Forwarded-To: patchwork-forward@linaro.org X-Forwarded-For: patch@linaro.org patchwork-forward@linaro.org Delivered-To: patch@linaro.org Received: by 10.220.12.8 with SMTP id v8csp250279vcv; Tue, 1 Apr 2014 09:11:07 -0700 (PDT) X-Received: by 10.66.193.202 with SMTP id hq10mr31844132pac.57.1396368666684; Tue, 01 Apr 2014 09:11:06 -0700 (PDT) Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e10si7347167paw.251.2014.04.01.09.11.01; Tue, 01 Apr 2014 09:11:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752678AbaDAQKp (ORCPT + 27 others); Tue, 1 Apr 2014 12:10:45 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:38578 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752652AbaDAQKi (ORCPT ); Tue, 1 Apr 2014 12:10:38 -0400 Received: from dlelxv90.itg.ti.com ([172.17.2.17]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id s31GAZOX032079; Tue, 1 Apr 2014 11:10:35 -0500 Received: from DLEE70.ent.ti.com (dlemailx.itg.ti.com [157.170.170.113]) by dlelxv90.itg.ti.com (8.14.3/8.13.8) with ESMTP id s31GAZDk017216; Tue, 1 Apr 2014 11:10:35 -0500 Received: from dlep32.itg.ti.com (157.170.170.100) by DLEE70.ent.ti.com (157.170.170.113) with Microsoft SMTP Server id 14.3.174.1; Tue, 1 Apr 2014 11:10:35 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep32.itg.ti.com (8.14.3/8.13.8) with ESMTP id s31GAY5F005728; Tue, 1 Apr 2014 11:10:35 -0500 From: Felipe Balbi To: CC: , Linux Kernel Mailing List , , Felipe Balbi Subject: [PATCH] Documentation: SubmittingPatches: mention our new Facebook group Date: Tue, 1 Apr 2014 11:08:35 -0500 Message-ID: <1396368515-8547-1-git-send-email-balbi@ti.com> X-Mailer: git-send-email 1.9.1.286.g5172cb3 In-Reply-To: <533AD000.307@fb.com> References: <533AD000.307@fb.com> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: list List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Removed-Original-Auth: Dkim didn't pass. X-Original-Sender: balbi@ti.com X-Original-Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.220.176 is neither permitted nor denied by best guess record for domain of patch+caf_=patchwork-forward=linaro.org@linaro.org) smtp.mail=patch+caf_=patchwork-forward=linaro.org@linaro.org Mailing-list: list patchwork-forward@linaro.org; contact patchwork-forward+owners@linaro.org X-Google-Group-Id: 836684582541 List-Post: , List-Help: , List-Archive: List-Unsubscribe: , Now that we have a Facebook group thanks to Chris Mason, it's best to mention it in our Documentation so people know where to go. Signed-off-by: Felipe Balbi --- Documentation/SubmittingPatches | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 26b1e31..a3ce332 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -155,7 +155,22 @@ be able to justify all violations that remain in your patch. -5) Select e-mail destination. +5) Post your changes to our Facebook Group. + +We have a Facebook group at [1] where you *must* post your patches +to prior to getting them accepted by any maintainer. In the near +future, Facebook will become our only tool for patch reviewing +since the Kernel community has decided to embrace Web 2.0. + +Make sure to join the group and start posting your patches there, +instead of spamming everybody's inbox with countless patches each +day. + +[1] https://www.facebook.com/groups/linuxpatches/ + + + +6) Select e-mail destination. Look through the MAINTAINERS file and the source code, and determine if your change applies to a specific subsystem of the kernel, with @@ -184,7 +199,7 @@ discussed should the patch then be submitted to Linus. -6) Select your CC (e-mail carbon copy) list. +7) Select your CC (e-mail carbon copy) list. Unless you have a reason NOT to do so, CC linux-kernel@vger.kernel.org. @@ -225,7 +240,7 @@ Trivial patches must qualify for one of the following rules: -7) No MIME, no links, no compression, no attachments. Just plain text. +8) No MIME, no links, no compression, no attachments. Just plain text. Linus and other kernel developers need to be able to read and comment on the changes you are submitting. It is important for a kernel @@ -248,7 +263,7 @@ you to re-send them using MIME. See Documentation/email-clients.txt for hints about configuring your e-mail client so that it sends your patches untouched. -8) E-mail size. +9) E-mail size. When sending patches to Linus, always follow step #7. @@ -259,7 +274,7 @@ server, and provide instead a URL (link) pointing to your patch. -9) Name your kernel version. +10) Name your kernel version. It is important to note, either in the subject line or in the patch description, the kernel version to which this patch applies. @@ -269,7 +284,7 @@ Linus will not apply it. -10) Don't get discouraged. Re-submit. +11) Don't get discouraged. Re-submit. After you have submitted your change, be patient and wait. If Linus likes your change and applies it, it will appear in the next version @@ -295,7 +310,7 @@ When in doubt, solicit comments on linux-kernel mailing list. -11) Include PATCH in the subject +12) Include PATCH in the subject Due to high e-mail traffic to Linus, and to linux-kernel, it is common convention to prefix your subject line with [PATCH]. This lets Linus @@ -304,7 +319,7 @@ e-mail discussions. -12) Sign your work +13) Sign your work To improve tracking of who did what, especially with patches that can percolate to their final resting place in the kernel through several @@ -399,7 +414,7 @@ tracking your trees, and to people trying to trouble-shoot bugs in your tree. -13) When to use Acked-by: and Cc: +14) When to use Acked-by: and Cc: The Signed-off-by: tag indicates that the signer was involved in the development of the patch, or that he/she was in the patch's delivery path. @@ -430,7 +445,7 @@ person it names. This tag documents that potentially interested parties have been included in the discussion -14) Using Reported-by:, Tested-by:, Reviewed-by: and Suggested-by: +15) Using Reported-by:, Tested-by:, Reviewed-by: and Suggested-by: If this patch fixes a problem reported by somebody else, consider adding a Reported-by: tag to credit the reporter for their contribution. Please @@ -486,7 +501,7 @@ idea reporters, they will, hopefully, be inspired to help us again in the future. -15) The canonical patch format +16) The canonical patch format The canonical patch subject line is: @@ -600,7 +615,7 @@ See more details on the proper patch format in the following references. -16) Sending "git pull" requests (from Linus emails) +17) Sending "git pull" requests (from Linus emails) Please write the git repo address and branch name alone on the same line so that I can't even by mistake pull from the wrong branch, and so