On Wed, Jun 09, 2021 at 09:58:44AM +0300, Tony Lindgren wrote: > * Greg KH <greg@xxxxxxxxx> [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. thanks, greg k-h
