From: Hans de Goede <hdegoede@redhat.com>
To: Chucheng Luo <luochucheng@vivo.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: wenhu.wang@vivo.com, trivial@kernel.org
Subject: Re: [PATCH] fs: Fix missing 'bit' in comment
Date: Fri, 13 Mar 2020 11:45:13 +0100 [thread overview]
Message-ID: <dfd44b01-3d90-3923-2971-d8d5bce5db08@redhat.com> (raw)
In-Reply-To: <20200313014655.28967-1-luochucheng@vivo.com>
Hi,
On 3/13/20 2:46 AM, Chucheng Luo wrote:
> The missing word may make it hard for other developers to
> understand it.
>
> Signed-off-by: Chucheng Luo <luochucheng@vivo.com>
This new version also looks good to me:
Acked-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
p.s.
In the future please mark new versions as such by using e.g.:
git send-email --subject-prefix="PATCH v2" ...
Actually, it would be good to resend this patch (with my
Acked-by added to the commit msg) this way because now there
is no way for the fs maintainers to figure out which one
of the 2 patches you've send out to apply.
> ---
> fs/vboxsf/dir.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/vboxsf/dir.c b/fs/vboxsf/dir.c
> index dd147b490982..4d569f14a8d8 100644
> --- a/fs/vboxsf/dir.c
> +++ b/fs/vboxsf/dir.c
> @@ -134,7 +134,7 @@ static bool vboxsf_dir_emit(struct file *dir, struct dir_context *ctx)
> d_type = vboxsf_get_d_type(info->info.attr.mode);
>
> /*
> - * On 32 bit systems pos is 64 signed, while ino is 32 bit
> + * On 32-bit systems pos is 64-bit signed, while ino is 32-bit
> * unsigned so fake_ino may overflow, check for this.
> */
> if ((ino_t)(ctx->pos + 1) != (u64)(ctx->pos + 1)) {
>
next prev parent reply other threads:[~2020-03-13 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 1:46 [PATCH] fs: Fix missing 'bit' in comment Chucheng Luo
2020-03-13 10:45 ` Hans de Goede [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-14 1:34 Chucheng Luo
2020-03-12 7:40 Chucheng Luo
2020-03-12 10:40 ` Hans de Goede
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=dfd44b01-3d90-3923-2971-d8d5bce5db08@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luochucheng@vivo.com \
--cc=trivial@kernel.org \
--cc=wenhu.wang@vivo.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).