From: Chuanhong Guo <gch981213@gmail.com>
To: KR Kim <kr.kim@skyhighmemory.com>
Cc: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
mmkurbanov@salutedevices.com, ddrokosov@sberdevices.ru,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
moh.sardi@skyhighmemory.com, changsub.shim@skyhighmemory.com
Subject: Re: [PATCH 2/2] SPI Nand Patch code for SkyHigh Momory
Date: Wed, 6 Mar 2024 16:10:13 +0800 [thread overview]
Message-ID: <CAJsYDVLHNODkL3zg-X6fP8N_FPFtReP_poFBua3kJHJ6m-a7Hw@mail.gmail.com> (raw)
In-Reply-To: <20240306041532.16985-1-kr.kim@skyhighmemory.com>
Hello!
On Wed, Mar 6, 2024 at 12:16 PM KR Kim <kr.kim@skyhighmemory.com> wrote:
>
> ---
> drivers/mtd/nand/spi/Makefile | 2 +-
> drivers/mtd/nand/spi/skyhigh.c | 57 ++++++----------------------------
> 2 files changed, 11 insertions(+), 48 deletions(-)
You should send an updated version of your original patch with
requested changes, not a new patch on top of your original one.
And your current patch is missing a proper title and commit message.
I believe there are multiple docs and tutorials online for submitting
patches to the Linux kernel, for example this one:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Read through the docs first before submitting your changes.
--
Regards,
Chuanhong Guo
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2024-03-06 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 4:15 [PATCH 2/2] SPI Nand Patch code for SkyHigh Momory KR Kim
2024-03-06 8:07 ` Miquel Raynal
2024-03-06 8:10 ` Chuanhong Guo [this message]
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=CAJsYDVLHNODkL3zg-X6fP8N_FPFtReP_poFBua3kJHJ6m-a7Hw@mail.gmail.com \
--to=gch981213@gmail.com \
--cc=changsub.shim@skyhighmemory.com \
--cc=ddrokosov@sberdevices.ru \
--cc=kr.kim@skyhighmemory.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mmkurbanov@salutedevices.com \
--cc=moh.sardi@skyhighmemory.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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 read-only IMAP folder(s) and NNTP newsgroup(s).