linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yan Zheng" <yanzheng@21cn.com>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Why the third parameter of "ext4_ext_put_in_cache" is __u32?
Date: Thu, 26 Jul 2007 22:57:59 +0800	[thread overview]
Message-ID: <3d0408630707260757w2bd53a2ey6ed1c11f06cd35be@mail.gmail.com> (raw)
In-Reply-To: <3d0408630707260754w71df514bh719a6e40cc6e2fdb@mail.gmail.com>

sorry, I mean the fourth parameter of "ext4_ext_put_in_cache.


2007/7/26, Yan Zheng <yanzheng@21cn.com>:
> Hi all
>
>   The third parameter of "ext4_ext_put_in_cache" is used to receive
> physical block number. I think the data type should be "ext4_fsblk_t".
>
> Thanks in advance.
>
> YZ
>

      reply	other threads:[~2007-07-26 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 14:54 Why the third parameter of "ext4_ext_put_in_cache" is __u32? Yan Zheng
2007-07-26 14:57 ` Yan Zheng [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=3d0408630707260757w2bd53a2ey6ed1c11f06cd35be@mail.gmail.com \
    --to=yanzheng@21cn.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).