From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964886AbbENRxi (ORCPT ); Thu, 14 May 2015 13:53:38 -0400 Received: from tex.lwn.net ([70.33.254.29]:45865 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932975AbbENRxg (ORCPT ); Thu, 14 May 2015 13:53:36 -0400 Date: Thu, 14 May 2015 13:53:33 -0400 From: Jonathan Corbet To: Luke Dashjr Cc: trivial@kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] SubmittingPatches: Clarify requirements for patches directed toward stable Message-ID: <20150514135333.76b25cf6@lwn.net> In-Reply-To: <201505140006.52131.luke@dashjr.org> References: <201505140006.52131.luke@dashjr.org> Organization: LWN.net X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 14 May 2015 00:06:48 +0000 Luke Dashjr wrote: > I misunderstood this section as simply asking me to add an email Cc, and > was unaware of the existence of Documentation/stable_kernel_rules.txt. > Hopefully this clarification will help save maintainers and new/rare > submitters time in the future. It's a good change, but I think it's worth going a bit further: you really don't need to email the patch to stable@ at all if the CC line appears in the patch itself. The patch will automatically come to the attention of the right folks once the patch hits the mainline. jon