linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guohua Zhong <zhongguohua1@huawei.com>
To: <richard.weinberger@gmail.com>
Cc: <joern@lazybastard.org>, <linux-kernel@vger.kernel.org>,
	<linux-mtd@lists.infradead.org>, <miquel.raynal@bootlin.com>,
	<nixiaoming@huawei.com>, <patrick@baymotion.com>,
	<richard@nod.at>, <vigneshr@ti.com>, <wangle6@huawei.com>,
	<young.liuyang@huawei.com>, <zhongguohua1@huawei.com>
Subject: Re: Re: [PATCH v2] phram: Allow the user to set the erase page size.
Date: Mon, 7 Dec 2020 15:07:15 +0800	[thread overview]
Message-ID: <20201207070715.15016-1-zhongguohua1@huawei.com> (raw)
In-Reply-To: <CAFLxGvxSycd=6WE4=XnrXxuF2Bc6A6ULA8GfkT8QvgcX=2Gk8g@mail.gmail.com>

On Mon, Dec 7, 2020 at 14:56 AM Guohua Zhong <zhongguohua1@huawei.com> wrote:
>
>> Permit the user to specify the erase page size as a parameter.
>> This solves two problems:
>
>> - phram can access images made by mkfs.jffs2.  mkfs.jffs2 won't
>> create images with erase sizes less than 8KiB; many architectures
>> define PAGE_SIZE as 4KiB.
>
>> - Allows more effective use of small capacity devices.  JFFS2
>> needs somewhere between 2 and 5 empty pages for garbage collection;
>> and for an NVRAM part with only 32KiB of space, a smaller erase page
>> allows much better utilization in applications where garbage collection
>> is important.
>
>> Signed-off-by: Patrick O'Grady <patrick@baymotion.com>
>> Reviewed-by: Joern Engel <joern@logfs.org>
>> Link: https://lore.kernel.org/lkml/CAJ7m5OqYv_=JB9NhHsqBsa8YU0DFRoP7C+W10PY22wonAGJK=A@mail.gmail.com/
>> [Guohua Zhong: fix token array index out of bounds and update patch for kernel master branch]
>> Signed-off-by: Guohua Zhong <zhongguohua1@huawei.com>
>> Reported-by: kernel test robot <lkp@intel.com>
>
> Looks good to me, except the authorship.
> If I understand correctly, you took this old patch and resend it.
> Please make sure that the "From:"-Line contains the original author.
> You can fix this up using git commit --amend --author=.
> The git format-patch will create a correct patch.

Sorry, I am not clear this rule before. But I found the same issue independently. It looks good 
after changging the erase size for phram driver. Then when I try to send the patch, I found that 
Patrick O'Grady has already send a patch which has not been merged as the link below
https://lore.kernel.org/lkml/CAJ7m5OqYv_=JB9NhHsqBsa8YU0DFRoP7C+W10PY22wonAGJK=A@mail.gmail.com/

So I resend a patch with some change and fix for mainline kernel with the old patch link of Patrick O'Grady.

If I need to change the authorship, I will resend this patch for V3 with authorship of Patrick O'Grady.

-- 
Thanks,
//guohua

  reply	other threads:[~2020-12-07  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25  7:11 [PATCH v2] phram: Allow the user to set the erase page size Guohua Zhong
2020-12-04  8:08 ` ping: " Guohua Zhong
2020-12-04  8:52 ` Richard Weinberger
2020-12-07  7:07   ` Guohua Zhong [this message]
2020-12-07  7:56     ` Miquel Raynal

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=20201207070715.15016-1-zhongguohua1@huawei.com \
    --to=zhongguohua1@huawei.com \
    --cc=joern@lazybastard.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=nixiaoming@huawei.com \
    --cc=patrick@baymotion.com \
    --cc=richard.weinberger@gmail.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    --cc=wangle6@huawei.com \
    --cc=young.liuyang@huawei.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).