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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 635DEC47083 for ; Fri, 4 Jun 2021 15:42:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3E56F61406 for ; Fri, 4 Jun 2021 15:42:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229809AbhFDPnw (ORCPT ); Fri, 4 Jun 2021 11:43:52 -0400 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]:45577 "EHLO wout4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229864AbhFDPnw (ORCPT ); Fri, 4 Jun 2021 11:43:52 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 93A9B16A4; Fri, 4 Jun 2021 11:42:05 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 04 Jun 2021 11:42:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:content-transfer-encoding:in-reply-to; s=fm1; bh=c nEhANXPRZDZe5tabUinYP1OslNcvHT28YsdMUkGZUc=; b=bTN0i5c5tkRi82UzC tJ/WU6Q6XnQMCgYybXMF49mDCm4GnOMYtYA/G0W+IBuTH92xeSrVoyu7jHyI7/VK qDGeCS/mAr2GvmJjykTqU5zr0mJlD0sRQd6ArHwy8PanHcoTNjaGdbHm3w5/Ke81 kC4PglCxWTAURs9HDL6IkmBxIqh5AWNO+XxaDBbymjmBURWnb2ZJVxOxJwrsfPHR TZJnboxTTslNyp745QtbONugA21XHodSu2gA6ZWoOeuI+aJKFfmyqUBBY2vhP4v7 vB2C3PsGL+ZZSUd6u70f2IqF4+UhggS02BooJCFayHZVF5VGnRtuIB2OfrEAWiYg AKXyg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=cnEhANXPRZDZe5tabUinYP1OslNcvHT28YsdMUkGZ Uc=; b=hUA+3k9nxdCBKmif2NrVJ3fwoTva9NbdmYnHDF7lPnlJ2AtUBa6o+xdc4 2lM8tUaAB0qUI/x+Qmq8n4968luqMOIvssPAYX8TQj9VTrLvahA51uYAg5CcseqE NwUrXQmyr7fLL4U1QCB518toa+yMC830piO9mxiWHBOh+e/YNe9LX2t5Hg0RwO05 htduI/nh0vvNQNyI5yzaFhbOJ9EKFG6zt1tBDQIxFpTt/vX9vPeLb0H5P6oV08+7 OCXRsZ1EdgXYJKvR3lp9OsswIFsIxYqPY52t8kQFyBr9tgMimx3UV4Mvdy4Z32oY M9y8mEcnvrADv5rT4p+tttKFzblEw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedtuddgledvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtugfgjgesthekredttddtjeenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepgeeije euvdffuedvffdtteefuefhkeehgfeuffejveettdelgfeuudffffetfedtnecuffhomhgr ihhnpehkvghrnhgvlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 4 Jun 2021 11:42:04 -0400 (EDT) Date: Fri, 4 Jun 2021 17:42:02 +0200 From: Greg KH To: =?utf-8?Q?Lauren=C8=9Biu_P=C4=83ncescu?= Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Backporting fix for #199981 to 4.19.y? Message-ID: References: <5399984e-0860-170e-377e-1f4bf3ccb3a0@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Jun 04, 2021 at 04:50:19PM +0200, Laurențiu Păncescu wrote: > Hi Greg, > > On 6/3/21 11:19 AM, Greg KH wrote: > > That commit does not apply cleanly and I need a backported version. Can > > you do that and test it to verify it works and then send it to us to be > > applied? > > I now have a patch against linux-4.19.y, tested on my EeePC just now: the > battery status and discharge rate are shown correctly. > > I've never submitted a patch before, should I put "commit > upstream." as the first line of my commit message, followed by another line > stating which branch I would like this to be merged to? Should I also > include the original commit message of the backported commit? And then use > git format-patch? I just read through [1] and [2], but they don't say > anything specific about commit messages for backported patches. Yes, what you describe here should be great. Look at the stable mailing list archives on lore.kernel.org for other examples of this happening, https://lore.kernel.org/r/20210603162852.1814513-1-zsm@chromium.org is one example. thanks, greg k-h