Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4995898pxj; Wed, 9 Jun 2021 06:59:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy8rXhVsGc5t9xpo4CvQeP8iUAWT6bE62W0eohPgw7mqeKyM7yNosJejOXTgW569VSblXJa X-Received: by 2002:a17:906:1c49:: with SMTP id l9mr28829442ejg.39.1623247175458; Wed, 09 Jun 2021 06:59:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623247175; cv=none; d=google.com; s=arc-20160816; b=To7JtF+OiDuTMjmM80thGxuhdukrU2LpFJgsVMuVKf/LkXUAM68+0DKirvdWmOGBZt sUMpn4jWKMxh2AP9awQCyyKiJp+5HcctKUFmxUv+2jsisNubTHkmNXJj1rZMyovImZXY YlMdRuVSleWyz84eJNoXwlmqZVHeIfZkNNATmb17SDu32pQaaGqWd1WRbfgA3gY+D6B5 N9MCQnPR7GOZVPAElFxxxhfxKlhEN070KyJyYIWb6yJ8KYnQpXzczg0nw3z/15fYyntu nDk9MD5JzgAz5fUqzni61JXGywgE/9Owu1UZqyzPuS2ZRcr5LYN9LmF8VivFlYXox5g7 9pDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=JfsR+dDf4J4ler9Bx34l2FdmGF5t0BQJ/qRuyhzdfjg=; b=pyge4FmCB64EngAcNfnEnSmPXll2NXdMHpm/6kj7bXCKIfo1MviBfWSSqfQ4GUHNCJ h/odI07PPejHL+a104beAUHDlJzV/sc1eXMi9y4ND5ZCBiKoahBHGaltdaZ0Or1/q6im fBSQtvfOoUKomG3y+OiZDWdHBuqNN4yLnuqBFmqQfM61tDSm7gZwC1F3/j2MoxKyyqJL a3kT0V/EthdXXVitiFVew17/nCZdu2lD/DRKRB9SC1phsJbz6bkSbT1dhioUKle9dfz/ eDrq3L6q/u9Y19DClsysdfGEGwbsK1Mz5Oski3Ax29kPynOGxpJQ6UBWeekWFLhsy9JD 3lQA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f23si2280914ejj.287.2021.06.09.06.59.10; Wed, 09 Jun 2021 06:59:35 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237707AbhFIIwN (ORCPT + 99 others); Wed, 9 Jun 2021 04:52:13 -0400 Received: from muru.com ([72.249.23.125]:39892 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229740AbhFIIwN (ORCPT ); Wed, 9 Jun 2021 04:52:13 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id C759780F5; Wed, 9 Jun 2021 08:50:24 +0000 (UTC) Date: Wed, 9 Jun 2021 11:50:13 +0300 From: Tony Lindgren To: Greg KH Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Daniel Lezcano , Keerthy , Tero Kristo Subject: Re: [Backport for linux-5.4.y PATCH 2/4] ARM: OMAP2+: Prepare timer code to backport dra7 timer wrap errata i940 Message-ID: References: <20210602104625.6079-1-tony@atomide.com> <20210602104625.6079-2-tony@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Greg KH [210609 07:31]: > On Wed, Jun 09, 2021 at 09:58:44AM +0300, Tony Lindgren wrote: > > * Greg KH [210609 06:22]: > > > On Wed, Jun 09, 2021 at 09:13:53AM +0300, Tony Lindgren wrote: > > > > How about the following for the description: > > > > > > > > Upstream commit 52762fbd1c4778ac9b173624ca0faacd22ef4724 usage of > > > > struct dmtimer_clockevent backported to the platform timer code > > > > still used in linux-5.4.y stable kernel. Needed to backport upstream > > > > commit 3efe7a878a11c13b5297057bfc1e5639ce1241ce and commit > > > > 25de4ce5ed02994aea8bc111d133308f6fd62566. Earlier kernels use > > > > mach-omap2/timer instead of drivers/clocksource as these kernels still > > > > depend on legacy platform code for booting. > > > > > > Why are you combining 2 commits into one here? > > > > OK so still too confusing, how about let's just have: > > > > Upstream commit 52762fbd1c4778ac9b173624ca0faacd22ef4724 usage of > > struct dmtimer_clockevent backported to the platform timer code > > still used in linux-5.4.y stable kernel. > > Why not just use the normal commit message with the "upstream commit..." > message as the first line, and then in the s-o-b area add > [backported to 5.4.y - tony] > > That's the normal thing we do here for backporting. OK sure works for me thanks. I will repost the series with updated patch descriptions. Regards, Tony