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.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,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 EF3AEC65BAF for ; Wed, 12 Dec 2018 21:43:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A634C20851 for ; Wed, 12 Dec 2018 21:43:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1544651021; bh=GOuKSNN5H9YU1nrhl9KwsW8w++o8IpBWzwsf7wTQQ2E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=ZEoAWsoInL+P4PGN93XwRi4+tseqiNuTjSVO17fzXT+5LV5VW03U7W6hGI9NWrIdk qjljKn4l8UyQAddI/Sl58otQytcBAw9VQIMSWOPfhIapvOz484lRg5PtnivwKX2jV9 VOLhrcT01ALsnOWoD2rPM4vbbKOG36Fkb4AN0E+8= DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A634C20851 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.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 S1728089AbeLLVnk (ORCPT ); Wed, 12 Dec 2018 16:43:40 -0500 Received: from mail.kernel.org ([198.145.29.99]:39148 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726263AbeLLVnk (ORCPT ); Wed, 12 Dec 2018 16:43:40 -0500 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (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 7BE8920672; Wed, 12 Dec 2018 21:43:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1544651018; bh=GOuKSNN5H9YU1nrhl9KwsW8w++o8IpBWzwsf7wTQQ2E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QiMCp4i+4UXG9B9GhsdiaHuh+lxclcViFicIdKaFGrq+9oiTBmTTKFUxVJ8oM7bMJ e8LM0XgfPfQrn/0wIzFzuzUKzHp1OzbS9RZ4pLVMhJvB7ZhRzEbavlVUXmy+c/iX7F XAWKw6TZ1ZRz2QACcVsu2K6QnKsEUSlzUmuUtJf4= Date: Wed, 12 Dec 2018 16:43:37 -0500 From: Sasha Levin To: Daniel Wang Cc: Sergey Senozhatsky , Petr Mladek , Sergey Senozhatsky , Steven Rostedt , stable@vger.kernel.org, Alexander.Levin@microsoft.com, Andrew Morton , byungchul.park@lge.com, dave.hansen@intel.com, hannes@cmpxchg.org, jack@suse.cz, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Mathieu Desnoyers , Mel Gorman , mhocko@kernel.org, pavel@ucw.cz, penguin-kernel@i-love.sakura.ne.jp, Peter Zijlstra , tj@kernel.org, Linus Torvalds , vbabka@suse.cz, Cong Wang , Peter Feiner Subject: Re: 4.14 backport request for dbdda842fe96f: "printk: Add console owner and waiter logic to load balance console writes" Message-ID: <20181212214337.GD2746@sasha-vm> References: <20181212052126.GF431@jagdpanzerIV> <20181212062841.GI431@jagdpanzerIV> <20181212064841.GB2746@sasha-vm> <20181212081034.GA32687@jagdpanzerIV> <20181212133603.yyu2zvw7g454zdqd@pathway.suse.cz> <20181212135939.GA10170@tigerII.localdomain> <20181212174333.GC2746@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: 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 On Wed, Dec 12, 2018 at 12:11:29PM -0800, Daniel Wang wrote: >On Wed, Dec 12, 2018 at 9:43 AM Sasha Levin wrote: >> >> On Wed, Dec 12, 2018 at 10:59:39PM +0900, Sergey Senozhatsky wrote: >> >On (12/12/18 14:36), Petr Mladek wrote: >> >> > OK, really didn't know that! I wasn't Cc-ed on that AUTOSEL email, >> >> > and I wasn't Cc-ed on this whole discussion and found it purely >> >> > accidentally while browsing linux-mm list. >> >> >> >> I am sorry that I did not CC you. There were so many people in CC. >> >> I expected that all people mentioned in the related commit message >> >> were included by default. >> > >> >No worries! I'm not blaming anyone. >> > >> >> > So if you are willing to backport this set to -stable, then I wouldn't >> >> > mind, probably would be more correct if we don't advertise this as a >> >> > "panic() deadlock fix" >> >> >> >> This should not be a problem. I guess that stable does not modify >> >> the original commit messages unless there is a change. >> > >> >Agreed. >> >> I'll be happy to add anything you want to the commit message. Do you >> have a blurb you want to use? > >If we still get to amend the commit message, I'd like to add "Cc: >stable@vger.kernel.org" in the sign-off area. According to >https://www.kernel.org/doc/html/v4.12/process/stable-kernel-rules.html#option-1 >patches with that tag will be automatically applied to -stable trees. >It's unclear though if it'll get applied to ALL -stable trees. For my >request, I care at least about 4.19 and 4.14. So maybe we can add two >lines, "Cc: # 4.14.x" and "Cc: > # 4.19.x". We can't change the original commit message (but that's fine, the purpose of that tag is to let us know that this commit should go in stable - and no we do :) ). I was under the impression that Sergey or Petr wanted to add more information about the purpose of this patch and the issue it solves. -- Thanks, Sasha