Re: [patch 4/4] Actually make the f_ops field const

Arjan van de Ven <[email protected]> wrote:
>
> Mark the f_ops members of inodes as const, as well as fix the ripple-through
>  this causes by places that copy this f_ops and then "do stuff" with it.
>  (some of the "do stuff" is quite unpleasant..)

Right now is the worst possible time in the kernel cycle to be raising
large many-file patches like this.  You need to either take a look at
what's coming in -mm or wait until all the git trees have merged up then do
the patch against -linus.

In this case there are mulitple new references to non-const file_operations
added to Linus's tree by alsa 48 hours ago.
-
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 4/4] Actually make the f_ops field const
    • From: Arjan van de Ven <[email protected]>

• References:
  • [patch 0/4] Series to allow a "const" file_operations struct
    • From: Arjan van de Ven <[email protected]>
  • [patch 4/4] Actually make the f_ops field const
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: [linux-pm] [patch] pm: fix runtime powermanagement's /sys interface
• Next by Date: Re: [PATCH 0/3] updated *at function patch
• Previous by thread: [patch 4/4] Actually make the f_ops field const
• Next by thread: Re: [patch 4/4] Actually make the f_ops field const
• 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]