Re: [patch 09/12] fuse: add list of writable files to fuse_inode

> hm.  At no point in this patch series does anything actually get added to
> these lists, so this patch is presently a no-op.
> 
> I'll assume that it will get used later.  But it is a bit odd to add
> infrastructure in a patch series, then not use it.  Why not hold the patch
> back and include it in the patch series which actually uses these lists for
> something?

My stupidity.  I somehow thought the patch does actually do something
interesting when including it in this series, instead of holding it
back for the writable-mmap series.

Miklos
-
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/

---

• References:
  • [patch 00/12] fuse update
    • From: Miklos Szeredi <[email protected]>
  • [patch 09/12] fuse: add list of writable files to fuse_inode
    • From: Miklos Szeredi <[email protected]>
  • Re: [patch 09/12] fuse: add list of writable files to fuse_inode
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [patch 12/12] fuse: add blksize field to fuse_attr
• Next by Date: Re: [PATCH] Version 3 (2.6.23-rc8) Smack: Simplified Mandatory Access Control Kernel
• Previous by thread: Re: [patch 09/12] fuse: add list of writable files to fuse_inode
• Next by thread: [patch 11/12] fuse: add support for mandatory locking
• 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]