public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Li kunyu <kunyu@nfschina.com>
Cc: krisman@collabora.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] unicode: mkutf8data: Add compound malloc function
Date: Mon, 24 Oct 2022 16:16:25 +0700	[thread overview]
Message-ID: <2edcbc94-e29a-b8ab-e320-ee52788471c8@gmail.com> (raw)
In-Reply-To: <20221024082619.178940-1-kunyu@nfschina.com>

On 10/24/22 15:26, Li kunyu wrote:
> 
> I send the 1/2 and 2/2 patches separately, and divide the two functions and related modifications in the 2/2 patch into two patches.
> 

No, not that way.

Here's the recipe for submitting patch series (a set of two or more patches),
assuming that you do the work on a branch which is based on mainline (master):

1. First, create directory which to store the patches.
2. Determine the base commit for your branch. Most of the times `git merge-base
   master <your branch>` can be used, but sometimes you need to determine that
   manually by seeing the commit log with `git log`.
3. Generate the patch series (preferably with cover letter) by `git format-patch
   -o <directory> --cover-letter --base=<base commit> <base commit>`. You can
   now write the description about the series in the cover letter (which will
   be 0000-cover-letter.patch).
4. Find the maintainers which will review your series with
   `scripts/get_maintainer.pl /path/to/directory/*.patch`. Ignore your email
   address if it exists.
5. Send the series with `git send-email <--to and/or --cc maintainers>
   /path/to/directory/*.patch`. All patches will be sent as reply to the
   cover letter.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara


      reply	other threads:[~2022-10-24  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  4:50 [PATCH 1/2] unicode: mkutf8data: Add compound malloc function Li kunyu
2022-10-24  7:56 ` Bagas Sanjaya
2022-10-24  8:26   ` Li kunyu
2022-10-24  9:16     ` Bagas Sanjaya [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=2edcbc94-e29a-b8ab-e320-ee52788471c8@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=krisman@collabora.com \
    --cc=kunyu@nfschina.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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