Re: [PATCH 1 of 2] fsstack: Introduce fsstack_copy_{attr,inode}_*

>To: [email protected]

(Superb idea to prekill any Cc, re-adding them)

>+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?


	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 1 of 2] fsstack: Introduce fsstack_copy_{attr,inode}_*
    • From: Josef Sipek <[email protected]>

• References:
  • [PATCH 1 of 2] fsstack: Introduce fsstack_copy_{attr,inode}_*
    • From: Josef "Jeff" Sipek <[email protected]>

• Prev by Date: Re: BUG dcache.c:613 during autofs unmounting in 2.6.19rc2
• Next by Date: Re: Would SSI clustering extensions be of interest to kernel community?
• Previous by thread: [PATCH 1 of 2] fsstack: Introduce fsstack_copy_{attr,inode}_*
• Next by thread: Re: [PATCH 1 of 2] fsstack: Introduce fsstack_copy_{attr,inode}_*
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]