From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andrew James Wade <andrew.j.wade@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
hch@infradead.org, Al Viro <viro@ftp.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
ezk@cs.sunysb.edu, mhalcrow@us.ibm.com
Subject: Re: [PATCH 1 of 2] fsstack: Introduce fsstack_copy_{attr,inode}_*
Date: Tue, 17 Oct 2006 16:33:39 -0400 [thread overview]
Message-ID: <20061017203339.GA30847@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <Pine.LNX.4.61.0610171237220.22888@yvahk01.tjqt.qr>
On Tue, Oct 17, 2006 at 12:40:31PM +0200, Jan Engelhardt wrote:
>
> >To: null@josefsipek.net
>
> (Superb idea to prekill any Cc, re-adding them)
Yeah, I like to test the emails but I accidentally sent them. From now on,
no testing :)
> >+void __fsstack_copy_attr_all(struct inode *dest,
> >+ const struct inode *src,
> >+ int (*get_nlinks)(struct inode *))
> >+{
> >[big]
> >+}
> >+
> >+/* externs for fs/stack.c */
> >+extern void __fsstack_copy_attr_all(struct inode *dest,
> >+ const struct inode *src,
> >+ int (*get_nlinks)(struct inode *));
> >+
> >+static inline void fsstack_copy_attr_all(struct inode *dest,
> >+ const struct inode *src)
> >+{
> >+ __fsstack_copy_attr_all(dest, src, NULL);
> >+}
>
> Do we really need this indirection? Can't __fsstack_copy_attr_all be
> named fsstack_copy_attr_all instead?
I suppose it could. There is no API-breakage to avoid.
Josef "Jeff" Sipek.
--
Computer Science is no more about computers than astronomy is about
telescopes.
- Edsger Dijkstra
next prev parent reply other threads:[~2006-10-17 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fe7c146c6457a4b288ab.1161060147@thor.fsl.cs.sunysb.edu>
2006-10-17 10:40 ` [PATCH 1 of 2] fsstack: Introduce fsstack_copy_{attr,inode}_* Jan Engelhardt
2006-10-17 20:33 ` Josef Sipek [this message]
[not found] <patchbomb.1161060146@thor.fsl.cs.sunysb.edu>
2006-10-17 4:42 ` Josef Jeff Sipek
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=20061017203339.GA30847@filer.fsl.cs.sunysb.edu \
--to=jsipek@fsl.cs.sunysb.edu \
--cc=akpm@osdl.org \
--cc=andrew.j.wade@gmail.com \
--cc=ezk@cs.sunysb.edu \
--cc=hch@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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).