[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zu1thIT0V11C4l-5@rhfedora>
Date: Fri, 20 Sep 2024 08:41:40 -0400
From: "John B. Wyatt IV" <jwyatt@...hat.com>
To: Peng Fan <peng.fan@....com>
Cc: "Peng Fan (OSS)" <peng.fan@....nxp.com>,
Thomas Renninger <trenn@...e.com>, Shuah Khan <shuah@...nel.org>,
John Kacur <jkacur@...hat.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] tools: power: cpupower: Allow overriding
cross-compiling envs
On Fri, Sep 20, 2024 at 09:01:49AM +0000, Peng Fan wrote:
> > > > V2:
> > > > subject update, commit log update in patch 1, 2 Use strerror in
> > > > patch 1 without patch 2, need update Makefile with 'CROSS =
> > [cross
> > > > toolchain path]/aarch64-poky-linux-'
> > >
> > > Version information is applied per commit patch. Not in the cover
> > > letter.
> > >
>
> Just get this from the page:
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#the-canonical-patch-format
> When sending a next version, add a patch changelog to the cover
> Letter or to individual patches explaining difference against
> previous submission
>
> So it is fine to put changelog in cover-letter?
Ah, my mistake. It is fine.
--
Sincerely,
John Wyatt
Software Engineer, Core Kernel
Red Hat
Powered by blists - more mailing lists