Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: Backporting fix for #199981 to 4.19.y?
To:     stable@vger.kernel.org
Cc:     linux-kernel@vger.kernel.org
References: <c75fcd12-e661-bc03-e077-077799ef1c44@gmail.com>
 <YLiNrCFFGEmltssD@kroah.com> <5399984e-0860-170e-377e-1f4bf3ccb3a0@gmail.com>
 <YLiel5ZEcq+mlshL@kroah.com>
From:   =?UTF-8?Q?Lauren=c8=9biu_P=c4=83ncescu?= <lpancescu@gmail.com>
Message-ID: <addc193a-5b19-f7f3-5f26-cdce643cd436@gmail.com>
Date:   Fri, 4 Jun 2021 16:50:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <YLiel5ZEcq+mlshL@kroah.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

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 <short-hash> 
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.

Thanks,
Laurențiu


[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html
[2] https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html