linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Andreas Dilger <adilger@whamcloud.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] misc: use ext2_ino_t instead of ino_t
Date: Wed, 30 Mar 2022 10:30:26 -0400	[thread overview]
Message-ID: <87y20rpl6l.fsf@collabora.com> (raw)
In-Reply-To: <20220329211712.25506-1-adilger@whamcloud.com> (Andreas Dilger's message of "Tue, 29 Mar 2022 15:17:12 -0600")

Andreas Dilger <adilger@whamcloud.com> writes:

> Some of the new fastcommit and casefold changes used the system
> "ino_t" instead of "ext2_ino_t" for handling filesystem inodes.
> This causes printf warnings if "ino_t" is of a different size.
> Use the library "ext2_ino_t" for consistency.
>
> Signed-off-by: Andreas Dilger <adilger@whamcloud.com>

Hi Andreas,

feel free to add

Reviewed-by: Gabriel Krisman Bertazi <krisman@collabora.com>

-- 
Gabriel Krisman Bertazi

      reply	other threads:[~2022-03-30 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 21:17 [PATCH] misc: use ext2_ino_t instead of ino_t Andreas Dilger
2022-03-30 14:30 ` Gabriel Krisman Bertazi [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=87y20rpl6l.fsf@collabora.com \
    --to=krisman@collabora.com \
    --cc=adilger@whamcloud.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).