From: Richard Akintola <princerichard17a@gmail.com>
To: Samuel Abraham <abrahamadekunle50@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
outreachy@lists.linux.dev, sudipm.mukherjee@gmail.com,
teddy.wang@siliconmotion.com, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] staging: sm750fb: change function naming style
Date: Mon, 7 Apr 2025 06:57:38 +0100 [thread overview]
Message-ID: <CAMyr_bLkvFBTpYehG4fs-tqVE18YBf53okddU2=i7+Rr-zbCsw@mail.gmail.com> (raw)
In-Reply-To: <CADYq+fY-twT=NruAmfb6EpmYJLM971aTu-CUi-We_Fd6JSP47Q@mail.gmail.com>
On Sat, Apr 5, 2025 at 3:16 PM Samuel Abraham
<abrahamadekunle50@gmail.com> 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 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.
Hi Samuel,
I sent the patches individually before, but I was instructed to send a
patch series.
Given that I didn't change any code, should I still add version number
and sending
patch series as the difference?
Richard Akintola
next prev parent reply other threads:[~2025-04-07 5:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 13:00 [PATCH 0/8] staging: sm750fb: change function naming style Richard Akintola
2025-04-05 13:00 ` [PATCH 1/8] staging: sm750fb: change sii164GetDeviceID to snake_case Richard Akintola
2025-04-05 13:00 ` [PATCH 2/8] staging: sm750fb: change sii164ResetChip " Richard Akintola
2025-04-05 13:00 ` [PATCH 3/8] staging: sm750fb: change sii164SetPower " Richard Akintola
2025-04-05 13:00 ` [PATCH 4/8] staging: sm750fb: change sii164GetChipString " Richard Akintola
2025-04-05 13:00 ` [PATCH 5/8] staging: sm750fb: change sii164EnableHotPlugDetection " Richard Akintola
2025-04-05 13:00 ` [PATCH 6/8] staging: sm750fb: change sii164IsConnected " Richard Akintola
2025-04-05 13:00 ` [PATCH 7/8] staging: sm750fb: change sii164CheckInterrupt " Richard Akintola
2025-04-05 13:00 ` [PATCH 8/8] staging: sm750fb: change sii164ClearInterrupt " Richard Akintola
2025-04-05 13:35 ` [PATCH 0/8] staging: sm750fb: change function naming style Greg KH
2025-04-05 14:07 ` Richard Akintola
2025-04-05 14:16 ` Samuel Abraham
2025-04-05 14:23 ` Samuel Abraham
2025-04-07 5:57 ` Richard Akintola [this message]
2025-04-07 5:59 ` Greg KH
2025-04-07 6:23 ` Richard Akintola
2025-04-08 10:38 ` Richard Akintola
2025-04-08 10:47 ` Greg KH
2025-04-08 11:03 ` Richard Akintola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMyr_bLkvFBTpYehG4fs-tqVE18YBf53okddU2=i7+Rr-zbCsw@mail.gmail.com' \
--to=princerichard17a@gmail.com \
--cc=abrahamadekunle50@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).