Re: [PATCH 2 of 23] lookup_one_len_nd - lookup_one_len with nameidata argument

On Sat, 2006-10-07 at 01:07 -0400, Josef Jeff Sipek wrote:

> -struct dentry * lookup_one_len(const char * name, struct dentry * base, int len)
> +struct dentry * lookup_one_len_nd(const char *name, struct dentry * base, int len, struct nameidata *nd)

> -extern struct dentry * lookup_one_len(const char *, struct dentry *, int);
> +extern struct dentry * lookup_one_len_nd(const char *, struct dentry *, int, struct nameidata *);
> +
> +/* SMP-safe */
> +static inline struct dentry *lookup_one_len(const char *name, struct dentry *dir, int len)


These lines are all too long . Should max out at 80 characters.

Daniel

-
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 2 of 23] lookup_one_len_nd - lookup_one_len with nameidata argument
    • From: Josef Sipek <[email protected]>

• References:
  • [PATCH 2 of 23] lookup_one_len_nd - lookup_one_len with nameidata argument
    • From: Josef "Jeff" Sipek <[email protected]>

• Prev by Date: Re: 2.6.19-rc1 genirq causes either boot hang or "do_IRQ: cannot handle IRQ -1"
• Next by Date: -git regression: Voyager compile error
• Previous by thread: [PATCH 2 of 23] lookup_one_len_nd - lookup_one_len with nameidata argument
• Next by thread: Re: [PATCH 2 of 23] lookup_one_len_nd - lookup_one_len with nameidata argument
• 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]