Re: [PATCH 0/8] staging: sm750fb: change function naming style

[Samuel Abraham <abrahamadekunle50@gmail.com>]

On Sat, Apr 5, 2025 at 3:07 PM Richard Akintola
<princerichard17a@gmail.com> wrote:
>
> On Sat, Apr 5, 2025 at 2:37 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > - This looks like a new version of a previously submitted patch, but you
> >   did not list below the --- line any changes from the previous version.
>
> Please, how do I resolve this issue?
>
> Richard Akintola

Hello Richard

THis is the main message from the bot

This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe this.

It basically means that if you made a change to a patch, you will have
a new version.
You will have to indicate the patch version and also what changed

So lets say you have a first Patch then after review, or you edited
the commit message
or made a change in the code or something,
you will now have a new patch which you will call v2.

you will use git format-patch -o /tmp/ --subject-prefix="PATCH v2" <commit-ID>

then when you want to send with mutt, immediately after the signed-off
by line there are three dashes (---),
You will then write what changes under these three dashes in the format

signedoff-by: Richard
---
Changes in v1:
   - This is what changed in v1.

I hope this helps

Adekunle.