mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Li Nan <linan666@huaweicloud.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Li Nan <linan666@huaweicloud.com>
Cc: corbet@lwn.net, song@kernel.org, yukuai3@huawei.com,
	xni@redhat.com, hare@suse.de, martin.petersen@oracle.com,
	bvanassche@acm.org, filipe.c.maia@gmail.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-raid@vger.kernel.org, yangerkun@huawei.com,
	yi.zhang@huawei.com
Subject: Re: [PATCH v4 2/2] md: allow configuring logical_block_size
Date: Fri, 12 Sep 2025 17:27:35 +0800	[thread overview]
Message-ID: <f2e02c19-98e8-30eb-1965-27b4c50ffeeb@huaweicloud.com> (raw)
In-Reply-To: <3759cfba-93a3-4252-99a3-97219e50bdf5@molgen.mpg.de>



在 2025/9/11 16:05, Paul Menzel 写道:
> Dear Nan,
> 
> 
> Thank you for your patch. Some minor nits. i’d write logical block size 
> without underscores in the summary and commit message body, if the variable 
> is not referenced.
> 

[...]

Hi Paul,

Thaks for your review. I'll address the points you mentioned in the next
patch version.

-- 
Thanks,
Nan


  reply	other threads:[~2025-09-12  9:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  7:31 [PATCH v4 0/2] make logical_block_size configurable linan666
2025-09-11  7:31 ` [PATCH v4 1/2] md: prevent adding disks with larger logical_block_size to active arrays linan666
2025-09-12  3:18   ` Xiao Ni
2025-09-12  9:20     ` Li Nan
2025-09-11  7:31 ` [PATCH v4 2/2] md: allow configuring logical_block_size linan666
2025-09-11  8:05   ` Paul Menzel
2025-09-12  9:27     ` Li Nan [this message]
2025-09-15  0:33   ` Xiao Ni
2025-09-15  2:15     ` Li Nan
2025-09-15  8:50       ` Xiao Ni
2025-09-16  6:33         ` Li Nan

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=f2e02c19-98e8-30eb-1965-27b4c50ffeeb@huaweicloud.com \
    --to=linan666@huaweicloud.com \
    --cc=bvanassche@acm.org \
    --cc=corbet@lwn.net \
    --cc=filipe.c.maia@gmail.com \
    --cc=hare@suse.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=song@kernel.org \
    --cc=xni@redhat.com \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@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
all inboxes | Powered by JetHome®