From: Markus Elfring <Markus.Elfring@web.de>
To: Namjae Jeon <namjae.jeon@samsung.com>, linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "Christoph Hellwig" <hch@lst.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sungjong Seo" <sj1557.seo@samsung.com>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Subject: Re: [PATCH v7 01/13] exfat: add in-memory and on-disk structures and headers
Date: Mon, 16 Dec 2019 14:50:25 +0100 [thread overview]
Message-ID: <088a50ad-dc67-4ff6-624d-a1ac2008b420@web.de> (raw)
In-Reply-To: <20191213055028.5574-2-namjae.jeon@samsung.com>
…
> +++ b/fs/exfat/exfat_fs.h
…
> +/* fatent.c */
…
> +int exfat_count_dir_entries(struct super_block *sb, struct exfat_chain *p_dir);
I have taken another look also at this function declaration.
1. Can any of these function parameters be marked as “const”?
2. Which source file should provide the corresponding implementation?
(I did not find it in the update step “[PATCH v7 06/13] exfat: add exfat
entry operations” so far.)
Regards,
Markus
next prev parent reply other threads:[~2019-12-16 13:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191213055336epcas1p267699d8a251e052da0ae8194cf5d1983@epcas1p2.samsung.com>
2019-12-13 5:50 ` [PATCH v7 00/13] add the latest exfat driver Namjae Jeon
[not found] ` <CGME20191213055337epcas1p24968ee98f2b2db80439c311a59b5d95b@epcas1p2.samsung.com>
2019-12-13 5:50 ` [PATCH v7 01/13] exfat: add in-memory and on-disk structures and headers Namjae Jeon
2019-12-16 13:50 ` Markus Elfring [this message]
2019-12-17 0:02 ` Namjae Jeon
2019-12-17 7:36 ` Markus Elfring
2019-12-17 7:56 ` Namjae Jeon
2019-12-17 13:10 ` Enrico Weigelt, metux IT consult
2019-12-18 0:09 ` 전남재/S/W Platform Lab(VD)/Staff Engineer/삼성전자
2019-12-18 9:33 ` Maurizio Lombardi
2019-12-19 11:20 ` Namjae Jeon
2019-12-16 15:26 ` Markus Elfring
[not found] ` <CGME20191213055338epcas1p12ac00549b7d5c92c16a7ff9afd814f94@epcas1p1.samsung.com>
2019-12-13 5:50 ` [PATCH v7 02/13] exfat: add super block operations Namjae Jeon
[not found] ` <CGME20191213055339epcas1p2ff141746e3bc076293c7633252387feb@epcas1p2.samsung.com>
2019-12-13 5:50 ` [PATCH v7 03/13] exfat: add inode operations Namjae Jeon
[not found] ` <CGME20191213055339epcas1p4c1c4b1646e2ec24f6a48c2f3010208a0@epcas1p4.samsung.com>
2019-12-13 5:50 ` [PATCH v7 04/13] exfat: add directory operations Namjae Jeon
[not found] ` <CGME20191213055340epcas1p424dbbfbabc709d2087058573463367a3@epcas1p4.samsung.com>
2019-12-13 5:50 ` [PATCH v7 05/13] exfat: add file operations Namjae Jeon
[not found] ` <CGME20191213055341epcas1p4340dae4923a8e512326f7be75a4426e1@epcas1p4.samsung.com>
2019-12-13 5:50 ` [PATCH v7 06/13] exfat: add exfat entry operations Namjae Jeon
[not found] ` <CGME20191213055341epcas1p291e09a7a59f59bfd6802e18987bec9e4@epcas1p2.samsung.com>
2019-12-13 5:50 ` [PATCH v7 07/13] exfat: add bitmap operations Namjae Jeon
[not found] ` <CGME20191213055342epcas1p2e9f2971a4a7d392173e885b446b3e2c3@epcas1p2.samsung.com>
2019-12-13 5:50 ` [PATCH v7 08/13] exfat: add exfat cache Namjae Jeon
[not found] ` <CGME20191213055342epcas1p384b8e47ce6b3689540b55202919165dc@epcas1p3.samsung.com>
2019-12-13 5:50 ` [PATCH v7 09/13] exfat: add misc operations Namjae Jeon
[not found] ` <CGME20191213055343epcas1p4cedc37fb1bd39d8b7ce5937aebbc30aa@epcas1p4.samsung.com>
2019-12-13 5:50 ` [PATCH v7 10/13] exfat: add nls operations Namjae Jeon
[not found] ` <CGME20191213055344epcas1p4445bead283b45a45eab868907774d529@epcas1p4.samsung.com>
2019-12-13 5:50 ` [PATCH v7 11/13] exfat: add Kconfig and Makefile Namjae Jeon
[not found] ` <CGME20191213055344epcas1p37b9d8fc36fce255eedc99a335feca564@epcas1p3.samsung.com>
2019-12-13 5:50 ` [PATCH v7 12/13] exfat: add exfat in fs/Kconfig and fs/Makefile Namjae Jeon
[not found] ` <CGME20191213055345epcas1p10a858f9ceb26f217e00183669947e500@epcas1p1.samsung.com>
2019-12-13 5:50 ` [PATCH v7 13/13] MAINTAINERS: add exfat filesystem Namjae Jeon
2019-12-18 7:30 ` [PATCH v7 00/13] add the latest exfat driver Markus Elfring
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=088a50ad-dc67-4ff6-624d-a1ac2008b420@web.de \
--to=markus.elfring@web.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=sj1557.seo@samsung.com \
--cc=valdis.kletnieks@vt.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).