Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hsiangkao@aol.com (Gao Xiang)
Subject: [Outreachy kernel] Re: [PATCH v3 2/2] staging: erofs: Modify conditional checks
Date: Tue, 6 Nov 2018 02:22:36 +0800	[thread overview]
Message-ID: <30e72aa4-e605-d087-364c-3b9f606edaec@aol.com> (raw)
In-Reply-To: <CAOMPgjgoseN=+1ezv+xDZSoWpUxnsA3f70NisjAwZN=113fj7w@mail.gmail.com>

Hi Bhagyashri,

On 2018/11/6 2:07, Bhagyashri Dighole wrote:
> Hi Gao,
> 
> In PATCH version v1 which is first stage of contribution, I modified data.c for all alignment changes and all conditional checks.?As per discussion on email for this patch, It was concluded that I need to re-submit patch for single change at a time.
> 
> So, I created PATCH v2. In this patch, I modified data.c only for single conditional check and single alignment change and committed accordingly. As per Gao?s suggestion to do all alignment change in a first patch and all conditional changes in another patch, I modified and created PATCH v3.
> 
> PATCH v3 is divided into two patches.
> 1) PATCH v3 1/2 has all alignment changes.
> 2) PATCH v3 2/2 has all conditional changes.

That is correct. However, you send two patchset of v3, see:

v3. the first time
1) https://lists.ozlabs.org/pipermail/linux-erofs/2018-November/000796.html
2) https://lists.ozlabs.org/pipermail/linux-erofs/2018-November/000797.html
2.1) https://lists.ozlabs.org/pipermail/linux-erofs/2018-November/000798.html
v3. the second time
1) https://lists.ozlabs.org/pipermail/linux-erofs/2018-November/000800.html
2) https://lists.ozlabs.org/pipermail/linux-erofs/2018-November/000801.html

It is hard for me to know which one is the latest version of your patchset.
If you send a newer version, you should use v4 instead of v3 (even if you
decide to add a changelog), or

If you resend the patchset (same as the previous one, just to remind us to review),
  you should use [PATCH v3 RESEND] for this case.

> 
> Also, I mentioned what changes each version of patch represents under ??-? symbol.

Yes, but I think you should use v4 rather than v3 to add a changelog as Greg mentioned.

> 
> I am not able to understand, where I am making mistake??Can you please help me?

That is my personal suggestion, maybe of some help for you...

Thanks,
Gao Xiang

  reply	other threads:[~2018-11-05 18:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 14:49 [PATCH v3 1/2] staging: erofs: Modify coding style alignments Bhagyashri P. Dighole
2018-11-05 12:35 ` [PATCH v3 2/2] staging: erofs: Modify conditional checks Bhagyashri P. Dighole
2018-11-05 14:03   ` Greg Kroah-Hartman
2018-11-05 14:50   ` Bhagyashri P. Dighole
2018-11-05 15:43   ` Gao Xiang
2018-11-05 15:50     ` [Outreachy kernel] " Julia Lawall
2018-11-05 18:07       ` Bhagyashri Dighole
2018-11-05 18:22         ` Gao Xiang [this message]
2018-11-05 19:08         ` Himanshu Jha
2018-11-05 15:37 ` [PATCH v3 1/2] staging: erofs: Modify coding style alignments Gao Xiang

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=30e72aa4-e605-d087-364c-3b9f606edaec@aol.com \
    --to=hsiangkao@aol.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