From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Tudor.Ambarus@microchip.com, linux-mtd@lists.infradead.org,
linux-mtd-request@lists.infradead.org
Subject: Re: Regards-cadence-quadspi changes to be submitted as patch to upstream
Date: Mon, 19 Aug 2019 10:04:28 +0800 [thread overview]
Message-ID: <6442de00-9388-28b3-bee0-7a87658778ca@linux.intel.com> (raw)
In-Reply-To: <480268df-0f8b-fa99-7d7d-43477b371493@ti.com>
Hi Vignesh,
Thank you so much for the response and your valuable information.
surely follow the same process before submitting the patches.
With Best Regards
Vadivel Murugan R
On 16/8/2019 6:53 PM, Vignesh Raghavendra wrote:
> Please follow guidelines at:
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html
> https://www.kernel.org/doc/html/latest/process/coding-style.html
>
> Run scripts/checkpatch.pl --strict on patches and fix the issues
> reported by the scripts before posting
>
> You can get list of people to cc by running ./scripts/get_maintainer.pl
> on the patch
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-08-19 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16568.1565684962.19300.linux-mtd@lists.infradead.org>
2019-08-13 10:03 ` Regards-cadence-quadspi changes to be submitted as patch to upstream Ramuthevar, Vadivel MuruganX
2019-08-13 10:45 ` Tudor.Ambarus
2019-08-14 1:11 ` Ramuthevar, Vadivel MuruganX
2019-08-16 10:53 ` Vignesh Raghavendra
2019-08-19 2:04 ` Ramuthevar, Vadivel MuruganX [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=6442de00-9388-28b3-bee0-7a87658778ca@linux.intel.com \
--to=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=linux-mtd-request@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--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 NNTP newsgroup(s).