All of lore.kernel.org
 help / color / mirror / Atom feed
From: IKEGAMI Tokunori <ikegami@allied-telesis.co.jp>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: PACKHAM Chris <chris.packham@alliedtelesis.co.nz>,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	"Boris Brezillon" <boris.brezillon@free-electrons.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: RE: [PATCH] mtd: cfi_cmdset_0002: Change write buffer to check correct value
Date: Wed, 9 May 2018 14:28:58 +0000	[thread overview]
Message-ID: <TY1PR01MB0954BC7ABCE51B0B22DA09BFDC990@TY1PR01MB0954.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20180509155319.170784df@bbrezillon>

Hi Boris-san,

Thank you so much for your support.
Okay I will do follow the process below.

> Just a few more tips regarding the submission process:
> 
> - you can group several patches in a patch series when some are
>   dependent on others. Just use 'git format-patch -<X>
>   <last-commit>' where <X> is the number of patches you want to generate
>   and <last-commit> is the last commit in the series. When you do that,
>   it's generally a good practice to have a cover letter explaining what
>   the patch series does. You can generate the cover letter with the
>   --cover-letter option
> 
> - when you send a new version of a patch or a patch series it should be
>   prefixed with "[PATCH vX ...]". This can be done by passing -v<X> (X
>   being the version number) to git format-patch
> 
> - when you send the exact same version of a patch or patch series
>   because the previous one has not been sent properly, you should
>   prefix the patches with "[PATCH RESEND ...]". Again, can be done by
>   passing --subject-prefix="PATCH RESEND" to git format-patch
> 
> - you should have a changelog describing what has changed between each
>   version of the patch or patchset. The changelog can be placed in the
>   cover-letter if you have one, or just after the "---" in the patch
>   itself. You can also add extra information that you don't want to
>   appear in the commit message just after this marker.

Regards,
Ikegami

      reply	other threads:[~2018-05-09 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180508044142.4159-1-ikegami@allied-telesis.co.jp>
2018-05-08  4:45 ` [PATCH] mtd: cfi_cmdset_0002: Change write buffer to check correct value smtpuser
2018-05-08  8:28   ` IKEGAMI Tokunori
2018-05-09 13:32     ` IKEGAMI Tokunori
2018-05-09 13:53       ` Boris Brezillon
2018-05-09 14:28         ` IKEGAMI Tokunori [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=TY1PR01MB0954BC7ABCE51B0B22DA09BFDC990@TY1PR01MB0954.jpnprd01.prod.outlook.com \
    --to=ikegami@allied-telesis.co.jp \
    --cc=boris.brezillon@bootlin.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.