/linux-4.1.27/Documentation/filesystems/ |
D | mandatory-locking.txt | 8 0. Why you should avoid mandatory locking 14 - The write system call checks for a mandatory lock only once 17 A process may then see file data change even while a mandatory 27 1. What is mandatory locking? 46 with a "mandatory" locking scheme, whereby the operating system kernel would 51 The System V mandatory locking scheme was intended to have as little impact as 53 as candidates for mandatory locking, and using the existing fcntl()/lockf() 59 to entire files, so the mandatory locking rules also have byte level 62 Note 2: POSIX.1 does not specify any scheme for mandatory locking, despite 63 borrowing the fcntl() locking scheme from System V. The mandatory locking [all …]
|
D | porting | 40 At some point that will become mandatory. 43 [mandatory] 67 [mandatory] 84 [mandatory] 95 [mandatory] 113 [mandatory] 123 [mandatory] 130 [mandatory] 152 [mandatory] 159 [mandatory] [all …]
|
D | locks.txt | 57 'Documentation/filesystems/mandatory-locking.txt' was prior to this release a 60 freeze an NFS server by asking it to read a file for which a mandatory lock 63 From this release of the kernel, mandatory locking can be turned on and off 65 The default is to disallow mandatory locking. The intention is that 66 mandatory locking only be enabled on a local filesystem as the specific need
|
D | 00-INDEX | 94 mandatory-locking.txt 95 - info on the Linux implementation of Sys V mandatory file locking.
|
D | exofs.txt | 107 This option is mandatory. integer can be
|
D | proc.txt | 1791 While the first three lines are mandatory and always printed, the rest is
|
/linux-4.1.27/net/dccp/ |
D | feat.c | 291 #define dccp_feat_print_opt(opt, feat, val, len, mandatory) do { \ argument 294 dccp_pr_debug_cat(") %s\n", mandatory ? "!" : ""); } while (0) 304 #define dccp_feat_print_opt(opt, feat, val, len, mandatory) argument 485 u8 mandatory, dccp_feat_val *fval) in dccp_feat_push_change() argument 498 new->needs_mandatory = mandatory; in dccp_feat_push_change() 701 u8 mandatory, u64 nn_val) in __feat_register_nn() argument 713 return dccp_feat_push_change(fn, feat, 1, mandatory, &fval); in __feat_register_nn() 726 u8 mandatory, u8 const *sp_val, u8 sp_len) in __feat_register_sp() argument 741 return dccp_feat_push_change(fn, feat, is_local, mandatory, &fval); in __feat_register_sp() 1305 static u8 dccp_feat_handle_nn_established(struct sock *sk, u8 mandatory, u8 opt, in dccp_feat_handle_nn_established() argument [all …]
|
D | options.c | 67 int mandatory = 0; in dccp_parse_options() local 110 if (mandatory) in dccp_parse_options() 113 mandatory = 1; in dccp_parse_options() 128 rc = dccp_feat_parse_options(sk, dreq, mandatory, opt, in dccp_parse_options() 244 mandatory = 0; in dccp_parse_options() 248 if (mandatory) in dccp_parse_options()
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | backend-api.txt | 224 (*) Name of cache provider [mandatory]: 232 (*) Allocate a new object [mandatory]: 247 (*) Look up and create object [mandatory]: 266 (*) Release lookup data [mandatory]: 274 (*) Increment object refcount [mandatory]: 283 (*) Lock/Unlock object [mandatory]: 302 (*) Check coherency state of an object [mandatory]: 311 (*) Update object [mandatory]: 320 (*) Invalidate data object [mandatory]: 332 (*) Discard object [mandatory]: [all …]
|
D | netfs-api.txt | 160 (1) The type of the object [mandatory]. 192 (4) A function to retrieve an object's key from the netfs [mandatory]. 266 (10) A function to unmark all the pages retaining cache metadata [mandatory].
|
/linux-4.1.27/drivers/net/wireless/ath/carl9170/ |
D | mac.c | 109 u32 basic, mandatory; in carl9170_set_mac_rates() local 124 mandatory = 0xff00; /* OFDM 6/9/12/18/24/36/48/54 */ in carl9170_set_mac_rates() 126 mandatory = 0xff0f; /* OFDM (6/9../54) + CCK (1/2/5.5/11) */ in carl9170_set_mac_rates() 130 carl9170_regwrite(AR9170_MAC_REG_MANDATORY_RATE, mandatory); in carl9170_set_mac_rates()
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | nfs41-server.txt | 23 focuses on the mandatory-to-implement NFSv4.1 Sessions, providing 28 the operations that are mandatory to implement (REQ), optional 143 * The spec claims this is mandatory, but we don't actually know of any 153 * mandatory only for servers that support CLAIM_DELEGATE_PREV and/or
|
D | Exporting | 116 fh_to_dentry (mandatory)
|
/linux-4.1.27/Documentation/i2c/ |
D | slave-interface | 62 * I2C_SLAVE_WRITE_REQUESTED (mandatory) 72 * I2C_SLAVE_READ_REQUESTED (mandatory) 81 * I2C_SLAVE_WRITE_RECEIVED (mandatory) 90 * I2C_SLAVE_READ_PROCESSED (mandatory) 104 * I2C_SLAVE_STOP (mandatory)
|
/linux-4.1.27/Documentation/devicetree/bindings/iio/adc/ |
D | mcp320x.txt | 4 all mandatory properties described in
|
/linux-4.1.27/Documentation/devicetree/bindings/ata/ |
D | atmel-at91_cf.txt | 7 and reset gpio's are mandatory while irq and vcc gpio's are
|
/linux-4.1.27/Documentation/devicetree/bindings/regulator/ |
D | ti-abb-regulator.txt | 83 1200000 3 0 0 0 0 /* RBB mandatory */ 84 1320000 1 0 0 0 0 /* FBB mandatory */ 105 1320000 1 0 0 0 0 /* FBB mandatory */
|
/linux-4.1.27/Documentation/devicetree/bindings/sound/ |
D | mvebu-audio.txt | 19 The first one is mandatory and defines the internal clock.
|
/linux-4.1.27/Documentation/devicetree/bindings/net/ |
D | marvell-pxa168.txt | 17 Each PHY can be represented as a sub-node. This is not mandatory.
|
D | fixed-link.txt | 12 * 'speed' (integer, mandatory), to indicate the link speed. Accepted
|
D | marvell-pp2.txt | 32 mandatory.
|
D | apm-xgene-enet.txt | 18 - First is the Rx interrupt. This irq is mandatory.
|
D | keystone-netcp.txt | 19 mandatory to have the ethernet switch sub-module for the ethernet interface to
|
/linux-4.1.27/Documentation/devicetree/bindings/watchdog/ |
D | marvel.txt | 17 - reg : A third entry is mandatory and should contain the
|
/linux-4.1.27/include/uapi/asm-generic/ |
D | Kbuild.asm | 9 # Headers that are mandatory in usr/include/asm/
|
/linux-4.1.27/include/linux/mfd/arizona/ |
D | core.h | 161 bool mandatory);
|
/linux-4.1.27/Documentation/devicetree/bindings/pci/ |
D | ralink,rt3883-pci.txt | 76 following mandatory properties: 84 mandatory properties as well:
|
D | mvebu-pci.txt | 58 PCIe interface, having the following mandatory properties:
|
/linux-4.1.27/Documentation/devicetree/bindings/media/i2c/ |
D | nokia,smia.txt | 32 Endpoint node mandatory properties
|
/linux-4.1.27/Documentation/devicetree/bindings/thermal/ |
D | st-thermal.txt | 28 Interrupt is mandatory to be defined when compatible is
|
D | exynos-thermal.txt | 46 Following properties are mandatory (depending on SoC):
|
/linux-4.1.27/security/smack/ |
D | Kconfig | 12 of other mandatory security schemes.
|
/linux-4.1.27/Documentation/devicetree/bindings/mmc/ |
D | sdhci-pxa.txt | 17 - reg names: should be "sdhci", "mbus", "conf-sdio3". only mandatory
|
/linux-4.1.27/Documentation/devicetree/bindings/media/xilinx/ |
D | xlnx,v-tpg.txt | 33 The xlnx,vtc and timing-gpios properties are mandatory when the TPG is
|
/linux-4.1.27/Documentation/hwmon/ |
D | ntc_thermistor | 89 name the mandatory global attribute, the thermistor name.
|
D | pmbus-core | 20 Unfortunately, while PMBus commands are standardized, there are no mandatory 188 is mandatory. 275 register. For such chips, checking the status register is mandatory when
|
D | sysfs-interface | 90 the only mandatory attribute.
|
/linux-4.1.27/Documentation/fmc/ |
D | identifiers.txt | 32 minimum mandatory subset - we create a simple structure and parse it 130 name. The IPMI-FRU name is not mandatory, but a strongly suggested 131 choice; the name filename is mandatory, because this is the preferred
|
D | FMC-and-SDB.txt | 62 SDB is not mandatory for use of this FMC kernel bus, but if you have SDB
|
/linux-4.1.27/drivers/iio/magnetometer/ |
D | Kconfig | 63 - st_magn (core functions for the driver [it is mandatory]);
|
/linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
D | renesas,gpio-rcar.txt | 29 mandatory if the hardware implements a controllable functional clock for
|
/linux-4.1.27/Documentation/devicetree/bindings/clock/ |
D | renesas,cpg-mstp-clocks.txt | 23 clocks. The first register is the clock control register and is mandatory.
|
/linux-4.1.27/Documentation/networking/ |
D | switchdev.txt | 51 mandatory to be implemented by all switch drivers
|
D | stmmac.txt | 95 This support also is mandatory for PTPv2 because the extra descriptors
|
D | packet_mmap.txt | 141 Binding the socket to your network interface is mandatory (with zero copy) to
|
/linux-4.1.27/Documentation/devicetree/bindings/leds/ |
D | common.txt | 35 flash LED; it is mandatory if the LED should
|
/linux-4.1.27/Documentation/virtual/kvm/ |
D | s390-diag.txt | 15 DIAGNOSE calls by the guest cause a mandatory intercept. This implies
|
D | api.txt | 1307 The KVM_DEV_ASSIGN_ENABLE_IOMMU flag is a mandatory option to ensure 2557 not mandatory.
|
/linux-4.1.27/Documentation/watchdog/ |
D | convert_drivers_to_kernel_api.txt | 37 Returns the mandatory watchdog_info struct from the driver 155 in 'watchdog-kernel-api.txt' in this directory. We pass it the mandatory
|
D | watchdog-kernel-api.txt | 88 /* mandatory operations */ 120 Some operations are mandatory and some are optional. The mandatory operations
|
/linux-4.1.27/Documentation/devicetree/bindings/bus/ |
D | imx-weim.txt | 47 Timing property for child nodes. It is mandatory, not optional.
|
/linux-4.1.27/Documentation/devicetree/bindings/input/ |
D | ads7846.txt | 5 all mandatory properties described in
|
/linux-4.1.27/drivers/iio/gyro/ |
D | Kconfig | 89 - st_gyro (core functions for the driver [it is mandatory]);
|
/linux-4.1.27/Documentation/devicetree/bindings/net/dsa/ |
D | dsa.txt | 37 Each port children node must have the following mandatory properties:
|
/linux-4.1.27/drivers/iio/pressure/ |
D | Kconfig | 95 - st_pressure (core functions for the driver [it is mandatory]);
|
/linux-4.1.27/drivers/iio/accel/ |
D | Kconfig | 63 - st_accel (core functions for the driver [it is mandatory]);
|
/linux-4.1.27/Documentation/ |
D | mailbox.txt | 24 Populate mbox_chan_ops, except peek_data() all are mandatory.
|
D | clk.txt | 193 Below is a matrix detailing which clk_ops are mandatory based upon the 195 mandatory, a cell marked as "n" implies that either including that
|
D | pwm.txt | 92 to have multiple PWM drivers in the system. For this reason it's mandatory
|
D | eisa.txt | 92 .probe and .remove members are mandatory.
|
D | hwspinlock.txt | 297 The first two callbacks are mandatory:
|
D | kobject.txt | 117 of the internal fields are setup with a (mandatory) call to kobject_init():
|
D | kmemcheck.txt | 91 debugging a problem. This option is not mandatory, however, because it slows
|
D | CodingStyle | 327 permitted -- although they are not mandatory in new code of your
|
D | SubmittingPatches | 464 the nature of your changes. While there is nothing mandatory about this, it
|
D | memory-barriers.txt | 1655 Mandatory barriers should not be used to control SMP effects, since mandatory 1746 This is a variation on the mandatory write barrier that causes writes to weakly
|
D | pinctrl.txt | 737 All the above functions are mandatory to implement for a pinmux driver.
|
/linux-4.1.27/Documentation/sound/oss/ |
D | AudioExcelDSP16 | 27 mandatory while some others are optional. Here a list of parameters you can
|
/linux-4.1.27/drivers/mfd/ |
D | arizona-core.c | 504 bool mandatory) in arizona_of_get_named_gpio() argument 510 if (mandatory) in arizona_of_get_named_gpio()
|
/linux-4.1.27/Documentation/scsi/ |
D | ufs.txt | 34 Support for Gear1 is mandatory (rate A: 1248Mbps, rate B: 1457.6Mbps)
|
D | libsas.txt | 275 - events marked M (mandatory) are mandatory (only one),
|
D | ChangeLog.megaraid | 405 are actually used. It is now mandatory for GCC 3.4.1 (current stable)
|
D | scsi_mid_low_api.txt | 722 Some are mandatory. Interface functions should be declared static. The
|
D | ChangeLog.1992-1997 | 769 more (i.e. the last mandatory) low-level changes to support
|
/linux-4.1.27/Documentation/gpio/ |
D | board.txt | 12 is mandatory) or ARCH_WANT_OPTIONAL_GPIOLIB (if GPIO support can be omitted) in
|
/linux-4.1.27/Documentation/video4linux/ |
D | pxa_camera.txt | 72 - an arrow with a comment is a mandatory transition (no condition)
|
/linux-4.1.27/Documentation/target/ |
D | tcm_mod_builder.txt | 27 tcm_mod_builder.py depends upon the mandatory '-p $PROTO_IDENT' and '-m
|
/linux-4.1.27/Documentation/powerpc/ |
D | cxl.txt | 304 in this struct. Currently all fields are mandatory. 326 this struct. Currently all fields are mandatory.
|
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
D | renesas,pfc-pinctrl.txt | 31 IRQ pins. This property is mandatory when the PFC handles GPIOs and
|
/linux-4.1.27/Documentation/frv/ |
D | booting.txt | 148 This is mandatory if "root=/dev/nfs" is given as an option. It tells the
|
D | kernel-ABI.txt | 64 No exceptions or interrupts may happen. Any mandatory exceptions
|
/linux-4.1.27/Documentation/power/powercap/ |
D | powercap.txt | 197 however, only one is mandatory.
|
/linux-4.1.27/Documentation/crypto/ |
D | api-intro.txt | 94 When submitting a new algorithm for inclusion, a mandatory requirement
|
D | asymmetric-keys.txt | 257 mandatory:
|
/linux-4.1.27/Documentation/networking/caif/ |
D | spi_porting.txt | 53 Only active edges are mandatory to be reported.
|
/linux-4.1.27/Documentation/filesystems/cifs/ |
D | README | 462 from failing on read and write if we use mandatory brlock style. 501 with cifs style mandatory byte range locks (and most 505 locking, send only mandatory lock requests. For some 507 DOS/Windows, which require Windows style mandatory byte range 509 forcing the cifs client to only send mandatory locks
|
D | CHANGES | 77 Add "forcemandatorylock" mount option to allow user to use mandatory 343 mandatory lock behavior such as Evolution), and also mount option for 1042 3) default file perms are now 2767 (indicating support for mandatory locks) instead of 777 for dire…
|
/linux-4.1.27/Documentation/device-mapper/ |
D | dm-raid.txt | 47 "stripe size". It is the only mandatory parameter and
|
/linux-4.1.27/Documentation/blockdev/ |
D | floppy.txt | 142 Sets the CMOS type of <drive> to <type>. This is mandatory if
|
/linux-4.1.27/drivers/gpu/drm/ |
D | drm_edid.c | 2738 const struct stereo_mandatory_mode *mandatory; in add_hdmi_mandatory_stereo_modes() local 2745 mandatory = &stereo_mandatory_modes[i]; in add_hdmi_mandatory_stereo_modes() 2750 new_mode->flags |= mandatory->flags; in add_hdmi_mandatory_stereo_modes()
|
/linux-4.1.27/Documentation/trace/ |
D | coresight.txt | 166 The "struct coresight_ops" is mandatory and will tell the framework how to
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | compress_offload.txt | 94 mandatory routines and possibly make use of optional ones.
|
D | hda_codec.txt | 60 for the last command. These two callbacks are mandatory and have to
|
/linux-4.1.27/Documentation/PCI/ |
D | pci.txt | 162 The vendor and device fields are mandatory, the others are optional. Users 169 entries defined in the driver. This makes the driver_data field mandatory
|
/linux-4.1.27/Documentation/ia64/ |
D | fsys.txt | 130 any other operation that would trigger mandatory RSE
|
/linux-4.1.27/drivers/net/wireless/brcm80211/brcmsmac/ |
D | main.c | 3429 u8 mandatory; in brcms_c_rate_lookup_init() local 3505 mandatory = BRCM_RATE_24M; in brcms_c_rate_lookup_init() 3507 mandatory = BRCM_RATE_12M; in brcms_c_rate_lookup_init() 3509 mandatory = BRCM_RATE_6M; in brcms_c_rate_lookup_init() 3512 mandatory = rate; in brcms_c_rate_lookup_init() 3515 br[rate] = mandatory; in brcms_c_rate_lookup_init()
|
/linux-4.1.27/Documentation/hid/ |
D | hid-transport.txt | 286 requests. This request is mandatory and hid core will reject the device if
|
/linux-4.1.27/Documentation/security/ |
D | Smack.txt | 7 Smack is a kernel based implementation of mandatory access 260 program can access up to users or programs. These schemes are called mandatory
|
D | keys.txt | 256 The security class "key" has been added to SELinux so that mandatory access 1108 The structure has a number of fields, some of which are mandatory:
|
/linux-4.1.27/Documentation/dmaengine/ |
D | provider.txt | 313 - This call is mandatory for slave operations only. This should NOT be
|
/linux-4.1.27/Documentation/vm/ |
D | transhuge.txt | 76 is by far not mandatory and khugepaged already can take care of long
|
/linux-4.1.27/Documentation/devicetree/ |
D | booting-without-of.txt | 528 zero terminated string and is mandatory for version 1 to 3 of the 629 through /chosen, like in this example, the platform type (mandatory) 966 This specification makes a few of these mandatory, but also defines
|
/linux-4.1.27/Documentation/usb/ |
D | gadget-testing.txt | 271 although it is not mandatory.
|
/linux-4.1.27/Documentation/development-process/ |
D | 4.Coding | 317 documentation has become essentially mandatory.
|
/linux-4.1.27/Documentation/netlabel/ |
D | draft-ietf-cipso-ipsecurity-01.txt | 46 mandatory access controls and multi-level security. These systems are
|
/linux-4.1.27/arch/arm/mm/ |
D | Kconfig | 1011 This option allows the use of custom mandatory barriers
|
/linux-4.1.27/Documentation/power/ |
D | pci.txt | 76 but it is mandatory for PCI Express devices. If a device supports the PCI PM 694 The PM callbacks in struct dev_pm_ops are not mandatory and if they are not
|
/linux-4.1.27/tools/lib/traceevent/ |
D | event-parse.c | 5521 int *offset, int *size, int mandatory) in parse_header_field() argument 5544 if (mandatory) { in parse_header_field()
|
/linux-4.1.27/Documentation/cgroups/ |
D | cgroups.txt | 533 Each subsystem may export the following methods. The only mandatory
|
/linux-4.1.27/drivers/i2c/busses/ |
D | Kconfig | 977 An adapter type parameter is now mandatory. Please read the file
|
/linux-4.1.27/Documentation/block/ |
D | biodoc.txt | 909 The functions an elevator may implement are: (* are mandatory)
|
/linux-4.1.27/init/ |
D | Kconfig | 528 making these warnings mandatory for the tree variants.
|
/linux-4.1.27/arch/x86/ |
D | Kconfig | 1751 This option makes kernel signature verification mandatory for
|
/linux-4.1.27/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 1498 The tap device is mandatory, but the others are optional. If the
|