| /linux-4.1.27/arch/tile/gxio/ |
| D | mpipe.c | 248 void gxio_mpipe_rules_init(gxio_mpipe_rules_t *rules, in gxio_mpipe_rules_init() argument
251 rules->context = context; in gxio_mpipe_rules_init()
252 memset(&rules->list, 0, sizeof(rules->list)); in gxio_mpipe_rules_init()
257 int gxio_mpipe_rules_begin(gxio_mpipe_rules_t *rules, in gxio_mpipe_rules_begin() argument
264 gxio_mpipe_rules_list_t *list = &rules->list; in gxio_mpipe_rules_begin()
268 (gxio_mpipe_rules_rule_t *) (list->rules + list->head); in gxio_mpipe_rules_begin()
284 if (head + pad + sizeof(*rule) >= sizeof(list->rules)) in gxio_mpipe_rules_begin()
297 rule = (gxio_mpipe_rules_rule_t *) (list->rules + list->head); in gxio_mpipe_rules_begin()
310 stacks ? stacks->stacks[i] : rules->context->__stacks. in gxio_mpipe_rules_begin()
338 int gxio_mpipe_rules_add_channel(gxio_mpipe_rules_t *rules, in gxio_mpipe_rules_add_channel() argument
[all …]
|
| /linux-4.1.27/Documentation/aoe/ |
| D | udev.txt | 1 # These rules tell udev what device nodes to create for aoe support.
11 # udev_rules="/etc/udev/rules.d/"
12 # bash# ls /etc/udev/rules.d/
13 # 10-wacom.rules 50-udev.rules
15 # /etc/udev/rules.d/60-aoe.rules
|
| D | udev-install.sh | 27 rules_d=/etc/udev/rules.d
|
| D | aoe.txt | 29 udev configuration rules provided in udev.txt (in this directory).
32 rules on your system.
|
| /linux-4.1.27/net/wireless/ |
| D | genregdb.awk | 24 rules = 0;
120 rules++
127 printf "\t.n_reg_rules = %d\n", rules
129 rules = 0;
|
| D | db.txt | 12 # regulatory rules that cover the regulatory domains you will be using. Your
|
| D | Kconfig | 156 bool "use statically compiled regulatory rules database" if EXPERT
161 the wireless regulatory rules described in net/wireless/db.txt
163 to using CRDA for defining regulatory rules for the kernel.
|
| D | nl80211.c | 9342 rule = &rdev->coalesce->rules[i]; in nl80211_send_coalesce_rules()
9418 rule = &coalesce->rules[i]; in cfg80211_rdev_free_coalesce()
9423 kfree(coalesce->rules); in cfg80211_rdev_free_coalesce()
9542 new_coalesce.rules = kcalloc(n_rules, sizeof(new_coalesce.rules[0]), in nl80211_set_coalesce()
9544 if (!new_coalesce.rules) in nl80211_set_coalesce()
9553 &new_coalesce.rules[i]); in nl80211_set_coalesce()
9575 tmp_rule = &new_coalesce.rules[i]; in nl80211_set_coalesce()
9580 kfree(new_coalesce.rules); in nl80211_set_coalesce()
|
| /linux-4.1.27/security/smack/ |
| D | Kconfig | 16 bool "Reporting on access granted by Smack rules"
20 Enable the bring-up ("b") access mode in Smack rules.
25 rules. The developer can use the information to
26 identify which rules are necessary and what accesses
|
| /linux-4.1.27/kernel/ |
| D | audit_watch.c | 54 struct list_head rules; /* anchor for krule->rlist */ member
120 WARN_ON(!list_empty(&watch->rules)); in audit_put_watch()
179 INIT_LIST_HEAD(&watch->rules); in audit_init_watch()
290 list_for_each_entry_safe(r, nextr, &owatch->rules, rlist) { in audit_update_watch()
311 list_add(&nentry->rule.rlist, &nwatch->rules); in audit_update_watch()
343 list_for_each_entry_safe(r, nextr, &w->rules, rlist) { in audit_remove_parent_watches()
405 list_add(&krule->rlist, &watch->rules); in audit_add_to_parent()
457 if (list_empty(&watch->rules)) { in audit_remove_watch_rule()
|
| D | audit_tree.c | 16 struct list_head rules; member
83 INIT_LIST_HEAD(&tree->rules); in alloc_tree()
475 list_for_each_entry_safe(rule, next, &tree->rules, rlist) { in kill_rules()
561 if (list_empty(&tree->rules) && !tree->goner) { in audit_remove_tree_rule()
719 list_add(&rule->rlist, &tree->rules); in audit_add_tree_rule()
725 list_add(&rule->rlist, &tree->rules); in audit_add_tree_rule()
772 list_del_init(&tree->rules); in audit_add_tree_rule()
|
| /linux-4.1.27/Documentation/dvb/ |
| D | udev.txt | 8 Nevertheless it's now possible to add proper udev rules so that the
32 like you know them. All real distributions out there scan the /etc/udev/rules.d
34 will tell you the directory where the rules are, most likely it's /etc/udev/rules.d/
|
| /linux-4.1.27/net/ceph/crush/ |
| D | crush.c | 130 if (map->rules) { in crush_destroy()
133 crush_destroy_rule(map->rules[b]); in crush_destroy()
134 kfree(map->rules); in crush_destroy()
|
| D | mapper.c | 41 if (map->rules[i] && in crush_find_rule()
42 map->rules[i]->mask.ruleset == ruleset && in crush_find_rule()
43 map->rules[i]->mask.type == type && in crush_find_rule()
44 map->rules[i]->mask.min_size <= size && in crush_find_rule()
45 map->rules[i]->mask.max_size >= size) in crush_find_rule()
782 rule = map->rules[ruleno]; in crush_do_rule()
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-block-dm | 7 Users: util-linux, device-mapper udev rules
16 Users: util-linux, device-mapper udev rules
25 Users: util-linux, device-mapper udev rules
|
| D | sysfs-bus-platform | 13 matching rules binding. Writing to driver_override does not
|
| D | sysfs-bus-amba | 12 This returns the device to standard matching rules binding.
|
| D | ima_policy | 11 by opening the file, writing the rules one at a time and
|
| D | sysfs-bus-pci | 275 This returns the device to standard matching rules binding.
|
| D | sysfs-bus-iio | 240 used for averaging is device specific. The converting rules for
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | directory-locking | 11 1) read access. Locking rules: caller locks directory we are accessing.
13 2) object creation. Locking rules: same as above.
15 3) object removal. Locking rules: caller locks parent, finds victim,
18 4) rename() that is _not_ cross-directory. Locking rules: caller locks
23 5) link creation. Locking rules:
30 rules:
44 The rules above obviously guarantee that all directories that are going to be
102 But locking rules for cross-directory rename guarantee that we do not
|
| D | Locking | 1 The text below describes the locking rules for VFS-related methods.
24 locking rules:
72 locking rules:
130 locking rules:
170 locking rules:
207 locking rules:
288 ->sync_page() locking rules are not well-defined - usually it is called
346 locking rules:
364 locking rules:
388 locking rules:
[all …]
|
| D | gfs2-glocks.txt | 1 Glock internal locking rules
37 with cache management. The following rules apply for the cache:
46 These rules are implemented using the various glock operations which
83 Locking rules for glock operations:
|
| D | 00-INDEX | 4 - info on locking rules as they pertain to Linux VFS.
73 - info on the Global File System 2 - Glock internal locking rules.
|
| D | debugfs.txt | 5 about a process, or sysfs, which has strict one-value-per-file rules,
6 debugfs has no rules at all. Developers can put any information they want
|
| D | files.txt | 33 appear atomic. Here are the locking rules for
|
| D | porting | 332 .d_compare() calling convention and locking rules are significantly
339 .d_hash() calling convention and locking rules are significantly
|
| D | mandatory-locking.txt | 59 to entire files, so the mandatory locking rules also have byte level
|
| D | vfs.txt | 974 Same locking and synchronisation rules as d_compare regarding
1132 to show all the currently active options. The rules are:
1143 from the above rules.
1145 The underlying reason for the above rules is to make sure, that a
|
| D | seq_file.txt | 73 itself. A seq_file implementation that is formatting firewall rules, for
|
| /linux-4.1.27/security/apparmor/include/ |
| D | file.h | 183 static inline void aa_free_file_rules(struct aa_file_rules *rules) in aa_free_file_rules() argument
185 aa_put_dfa(rules->dfa); in aa_free_file_rules()
186 aa_free_domain_entries(&rules->trans); in aa_free_file_rules()
|
| /linux-4.1.27/arch/tile/include/gxio/ |
| D | mpipe.h | 956 extern void gxio_mpipe_rules_init(gxio_mpipe_rules_t *rules,
977 extern int gxio_mpipe_rules_begin(gxio_mpipe_rules_t *rules,
988 extern int gxio_mpipe_rules_set_headroom(gxio_mpipe_rules_t *rules,
1002 extern int gxio_mpipe_rules_add_channel(gxio_mpipe_rules_t *rules,
1017 extern int gxio_mpipe_rules_commit(gxio_mpipe_rules_t *rules);
|
| /linux-4.1.27/Documentation/networking/ |
| D | tc-actions-env-rules.txt | 2 The "environmental" rules for authors of any new tc actions are:
23 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| D | policy-routing.txt | 12 5. Additional pruning rules. (not in kernel space).
57 Kernel routing policy rules
67 We scan rules list, and if a rule is matched, apply it.
70 to scan rules.
|
| D | netdevices.txt | 10 struct net_device allocation rules
48 struct net_device synchronization rules
98 struct napi_struct synchronization rules
|
| D | openvswitch.txt | 151 compatibility for applications that follow the rules listed under
181 The application could, following the flow compatibility rules above,
186 across kernel versions even though it follows the compatibility rules.
236 Other rules
239 The other rules for flow keys are much less subtle:
|
| D | regulatory.txt | 38 # Example file, should be put in /etc/udev/rules.d/regulatory.rules
197 rules built into the kernel itself may be desirable. To account
|
| D | tproxy.txt | 55 add rules like this to the iptables ruleset above:
|
| D | ipvs-sysctl.txt | 54 also handled by stateful firewall rules. That is, iptables rules
|
| D | 00-INDEX | 203 tc-actions-env-rules.txt
204 - rules for traffic control (tc) actions.
|
| D | operstates.txt | 19 and changeable from userspace under certain rules.
|
| D | netdev-features.txt | 138 protect against other callbacks (the rules you need to find out).
|
| D | netdev-FAQ.txt | 145 Before you jump to go do the above, do note that the normal stable rules
|
| D | scaling.txt | 289 CPU. These rules aim to ensure that a flow only moves to a new CPU when
|
| D | ip-sysctl.txt | 1074 address according to the rules for level 2.
|
| /linux-4.1.27/arch/um/os-Linux/skas/ |
| D | Makefile | 10 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/Documentation/arm/ |
| D | kernel_mode_neon.txt | 54 following rules and restrictions apply in the kernel:
88 kernel is by adhering to the following rules:
102 NEON assembler is supported with no additional caveats as long as the rules
110 supported as long as the rules above are followed.
117 observe the following in addition to the rules above:
|
| D | cluster-pm-race-avoidance.txt | 487 rules for the intermediate (non-outermost) cluster levels.
|
| /linux-4.1.27/fs/hostfs/ |
| D | Makefile | 11 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/Documentation/security/ |
| D | Smack.txt | 39 smackctl - load the Smack access rules
128 This interface allows modification of existing access control rules.
161 This interface allows access control rules in addition to
162 the system defined rules to be specified. The format accepted
173 This interface allows access control rules in addition to
174 the system defined rules to be specified. The format accepted
184 This interface allows process specific access rules to be
185 defined. These rules are only consulted if access would
190 This interface allows process specific access rules to be
191 defined. These rules are only consulted if access would
[all …]
|
| D | credentials.txt | 108 action, and searching one or more sets of rules to see whether the subject
112 There are two main sources of rules:
116 Sometimes the object will include sets of rules as part of its
127 A Linux file might also sport a POSIX ACL. This is a list of rules
132 The system as a whole may have one or more sets of rules that get
228 rules (policies) that say what operations a task with one label may do to
|
| /linux-4.1.27/tools/perf/util/ |
| D | strfilter.h | 29 struct strfilter *strfilter__new(const char *rules, const char **err);
|
| D | strfilter.c | 155 struct strfilter *strfilter__new(const char *rules, const char **err) in strfilter__new() argument
161 filter->root = strfilter_node__new(rules, &ep); in strfilter__new()
|
| /linux-4.1.27/arch/um/kernel/skas/ |
| D | Makefile | 15 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/arch/x86/um/os-Linux/ |
| D | Makefile | 13 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/arch/um/os-Linux/drivers/ |
| D | Makefile | 13 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/ |
| D | Kbuild | 41 # We use internal kbuild rules to avoid the "is up to date" message from make
58 # We use internal kbuild rules to avoid the "is up to date" message from make
|
| D | .gitignore | 10 # Normal rules
|
| D | MAINTAINERS | 104 X: Files and directories that are NOT maintained, same rules as F:
|
| /linux-4.1.27/tools/build/Documentation/ |
| D | Build.txt | 100 The build framework provides standard compilation rules to handle .S and .c
125 - Dependency rules generated by 'gcc -Wp,-MD,...'
132 e) Single rules
|
| /linux-4.1.27/Documentation/devicetree/bindings/misc/ |
| D | ti,dac7512.txt | 7 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
|
| /linux-4.1.27/drivers/usb/serial/ |
| D | Makefile-keyspan_pda_fw | 2 # some rules to handle the quirks of the 'as31' assembler, like
|
| /linux-4.1.27/Documentation/locking/ |
| D | lockdep-design.txt | 13 respect to locking rules, even if the locks may have multiple (possibly
44 When locking rules are violated, these state bits are presented in the
65 Single-lock state rules:
76 single-lock state rules.
78 Multi-lock dependency rules:
106 The above rules are enforced for any locking sequence that occurs in the
111 dependency rules are enforced:
210 The above rules require _massive_ amounts of runtime checking. If we did
|
| D | mutex-design.txt | 89 The mutex subsystem checks and enforces the following rules:
|
| /linux-4.1.27/Documentation/ABI/stable/ |
| D | sysfs-devices | 2 # is documented in Documentation/sysfs-rules.txt
|
| D | sysfs-bus-firewire | 38 Users: udev rules to set ownership and access permissions or ACLs of
133 Users: udev rules to create /dev/disk/by-id/ symlinks
|
| /linux-4.1.27/Documentation/sound/alsa/soc/ |
| D | pops_clicks.txt | 22 shutdown and follows some basic rules:-
36 ADC until all the pops have occurred. This follows similar power rules to
|
| /linux-4.1.27/Documentation/video4linux/bttv/ |
| D | README.quirks | 40 When using the 430FX PCI, the following rules will ensure
48 simple logical-or of video and audio requests would violate the rules.
54 rules are satisfied. Before GNT is asserted by the PCI arbiter, this
|
| /linux-4.1.27/drivers/staging/lustre/lustre/ptlrpc/ |
| D | sec_config.c | 257 struct sptlrpc_rule *rules; in sptlrpc_rule_set_expand() local
268 OBD_ALLOC(rules, nslot * sizeof(*rset->srs_rules)); in sptlrpc_rule_set_expand()
269 if (rules == NULL) in sptlrpc_rule_set_expand()
274 memcpy(rules, rset->srs_rules, in sptlrpc_rule_set_expand()
281 rset->srs_rules = rules; in sptlrpc_rule_set_expand()
|
| /linux-4.1.27/arch/um/os-Linux/ |
| D | Makefile | 20 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/net/bridge/netfilter/ |
| D | Kconfig | 44 The ebtables broute table is used to define rules that decide between
54 The ebtables filter table is used to define frame filtering rules at
63 The ebtables nat table is used to define rules that alter the MAC
83 MAC/IP address pairs can be matched, f.e. for anti-spoofing rules.
|
| /linux-4.1.27/net/netfilter/ |
| D | nf_tables_core.c | 134 rule = list_entry(&chain->rules, struct nft_rule, list); in nft_do_chain()
137 list_for_each_entry_continue_rcu(rule, &chain->rules, list) { in nft_do_chain()
|
| D | nf_tables_api.c | 278 list_for_each_entry(rule, &ctx->chain->rules, list) { in nft_delrule_by_chain()
1378 INIT_LIST_HEAD(&chain->rules); in nf_tables_newchain()
1685 list_for_each_entry(rule, &chain->rules, list) { in __nf_tables_rule_lookup()
1745 if ((event != NFT_MSG_DELRULE) && (rule->list.prev != &chain->rules)) { in nf_tables_fill_rule_info()
1831 list_for_each_entry_rcu(rule, &chain->rules, list) { in nf_tables_dump_rules()
2078 list_add_tail_rcu(&rule->list, &chain->rules); in nf_tables_newrule()
2083 list_add_rcu(&rule->list, &chain->rules); in nf_tables_newrule()
4131 list_for_each_entry(rule, &chain->rules, list) { in nf_tables_check_loops()
|
| D | Kconfig | 573 The target allows you to create rules in the "mangle" table which alter
690 It also adds the "TOS" target, which allows you to create rules in
718 The target allows you to create rules in the "raw" and "mangle" tables
769 This option adds a `LOG' target, which allows you to create rules in
875 For it to work you will have to configure certain iptables rules
888 the tables, chains, rules.
|
| /linux-4.1.27/arch/um/kernel/ |
| D | Makefile | 26 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/arch/x86/um/ |
| D | Makefile | 45 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/include/linux/crush/ |
| D | crush.h | 166 struct crush_rule **rules; member
|
| /linux-4.1.27/arch/tile/include/hv/ |
| D | drv_mpipe_intf.h | 573 uint8_t rules[4096 - 4]; member
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.diversion | 56 In this case all incoming calls are checked by rules that may be
60 The rules include primary and secondary service identifiers, called
88 To add and delete rules the additional divertctrl program is needed. This
|
| /linux-4.1.27/net/core/ |
| D | fib_rules.c | 704 static void attach_rules(struct list_head *rules, struct net_device *dev) in attach_rules() argument
708 list_for_each_entry(rule, rules, list) { in attach_rules()
718 static void detach_rules(struct list_head *rules, struct net_device *dev) in detach_rules() argument
722 list_for_each_entry(rule, rules, list) { in detach_rules()
|
| /linux-4.1.27/drivers/staging/media/bcm2048/ |
| D | TODO | 17 rules, and do evil tricks, like returning from a function inside a
|
| /linux-4.1.27/drivers/net/ethernet/broadcom/bnx2x/ |
| D | bnx2x_sp.c | 814 union eth_classify_rule_cmd *rule_entry = &data->rules[rule_idx]; in bnx2x_set_one_mac_e2()
998 union eth_classify_rule_cmd *rule_entry = &data->rules[rule_idx]; in bnx2x_set_one_vlan_e2()
2211 data->rules[rule_idx].client_id = p->cl_id; in bnx2x_set_rx_mode_e2()
2212 data->rules[rule_idx].func_id = p->func_id; in bnx2x_set_rx_mode_e2()
2214 data->rules[rule_idx].cmd_general_data = in bnx2x_set_rx_mode_e2()
2218 &(data->rules[rule_idx++]), in bnx2x_set_rx_mode_e2()
2224 data->rules[rule_idx].client_id = p->cl_id; in bnx2x_set_rx_mode_e2()
2225 data->rules[rule_idx].func_id = p->func_id; in bnx2x_set_rx_mode_e2()
2227 data->rules[rule_idx].cmd_general_data = in bnx2x_set_rx_mode_e2()
2231 &(data->rules[rule_idx++]), in bnx2x_set_rx_mode_e2()
[all …]
|
| D | bnx2x_hsi.h | 3781 union eth_classify_rule_cmd rules[CLASSIFY_RULES_COUNT]; member
3950 struct eth_filter_rules_cmd rules[FILTER_RULES_COUNT]; member
3966 union eth_classify_rule_cmd rules[CLASSIFY_RULES_COUNT]; member
4052 struct eth_multicast_rules_cmd rules[MULTICAST_RULES_COUNT]; member
|
| D | bnx2x_ethtool.c | 3259 u32 *rules __always_unused) in bnx2x_get_rxnfc()
|
| /linux-4.1.27/Documentation/devicetree/bindings/panel/ |
| D | samsung,ld9040.txt | 11 The panel must obey rules for SPI slave device specified in document [2].
|
| /linux-4.1.27/scripts/coccinelle/null/ |
| D | deref_null.cocci | 25 // The following two rules are separate, because both can match a single
212 // The following three rules are duplicates of ifm, pr1 and pr2 respectively.
|
| /linux-4.1.27/Documentation/ |
| D | sysfs-rules.txt | 11 of sysfs must follow some rules to use an as-abstract-as-possible way to
17 the following rules and then your programs should work with future
28 violates many of the rules in this document.
106 All three places have completely different rules on how to access
|
| D | kselftest.txt | 60 In general, the rules for for selftests are
|
| D | stable_kernel_rules.txt | 26 - It must follow the Documentation/SubmittingPatches rules.
57 Send the patch, after verifying that it follows the above rules, to
|
| D | ManagementStyle | 10 simple coding style rules, so this document may or may not have anything
147 There's just a few simple rules here:
226 you've followed the previous rules, you'll be pretty good at saying that
|
| D | volatile-considered-harmful.txt | 32 If all the code follows the locking rules, the value of shared_data cannot
|
| D | HOWTO | 99 patches if these rules are followed, and many people will only
109 Following these rules will not guarantee success (as all patches are
143 This file describes the rules on how the stable kernel releases
158 full description of the in-kernel API, and rules on how to handle
|
| D | pi-futex.txt | 14 abstraction, with strict rules that keep the implementation
|
| D | SubmittingDrivers | 42 The same rules apply as 2.4 except that you should follow linux-kernel
|
| D | kref.txt | 33 rules:
|
| D | 00-INDEX | 425 - rules and procedures for the -stable kernel releases.
430 sysfs-rules.txt
|
| D | printk-formats.txt | 104 The conversion rules are applied according to an optional combination
|
| D | cpu-hotplug.txt | 97 no locking rules as of now. Typical usage is to init topology during boot,
|
| D | bcache.txt | 49 bcache-tools now ships udev rules, and bcache devices are known to the kernel
|
| D | SubmittingPatches | 318 Trivial patches must qualify for one of the following rules:
417 pass it on as an open-source patch. The rules are pretty simple: if you
|
| D | CodingStyle | 341 EVER use a typedef unless you can clearly match one of those rules.
|
| D | DMA-API-HOWTO.txt | 113 set of rules regarding this, and this text is an attempt to finally
|
| D | memory-barriers.txt | 2512 address register if ordering rules are sufficiently relaxed:
2517 If ordering rules are relaxed, it must be assumed that accesses done inside an
|
| /linux-4.1.27/arch/um/drivers/ |
| D | Makefile | 67 include arch/um/scripts/Makefile.rules
|
| /linux-4.1.27/scripts/coccinelle/api/alloc/ |
| D | kzalloc-simple.cocci | 11 // URL: http://coccinelle.lip6.fr/rules/kzalloc.html
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | devices.txt | 115 For every propagated exception, the effective rules will be re-evaluated based
116 on current parent's access rules.
|
| D | blkio-controller.txt | 152 - One can specify per cgroup per device rules using this interface.
153 These rules override the default value of group weight as specified
326 Note: If both BW and IOPS rules are specified for a device, then IO is
|
| D | cpusets.txt | 205 The following rules apply to each cpuset:
211 These rules, and the natural hierarchy of cpusets, enable efficient
|
| D | unified-hierarchy.txt | 230 enabled, tasks are always only on the leaves. This rules out
|
| /linux-4.1.27/drivers/thermal/ti-soc-thermal/ |
| D | Kconfig | 21 This includes trip points definitions, extrapolation rules and
|
| /linux-4.1.27/Documentation/devicetree/bindings/ |
| D | ABI.txt | 18 II. General binding rules
|
| D | submitting-patches.txt | 6 0) Normal patch submission rules from Documentation/SubmittingPatches
|
| /linux-4.1.27/Documentation/devicetree/bindings/i2c/ |
| D | i2c-ocores.txt | 24 frequency. So the following rules are set to fix this situation:
|
| D | i2c-arb-gpio-challenge.txt | 7 the standard I2C multi-master rules. Using GPIOs is generally useful in
|
| /linux-4.1.27/net/openvswitch/ |
| D | Kconfig | 24 translate it into packet processing rules.
|
| /linux-4.1.27/net/ceph/ |
| D | osdmap.c | 192 c->rules = kcalloc(c->max_rules, sizeof(*c->rules), GFP_NOFS); in crush_decode()
193 if (c->rules == NULL) in crush_decode()
293 dout("rule vec is %p\n", c->rules); in crush_decode()
302 c->rules[i] = NULL; in crush_decode()
317 r = c->rules[i] = kmalloc(sizeof(*r) + in crush_decode()
|
| /linux-4.1.27/net/bridge/ |
| D | Kconfig | 27 take this into account when setting up your firewall rules.
|
| /linux-4.1.27/drivers/net/ethernet/tile/ |
| D | tilegx.c | 924 static gxio_mpipe_rules_t rules; /* too big to fit on the stack */ in tile_net_update() local
933 gxio_mpipe_rules_init(&rules, &md->context); in tile_net_update()
940 gxio_mpipe_rules_begin(&rules, md->first_bucket, in tile_net_update()
942 gxio_mpipe_rules_set_headroom(&rules, NET_IP_ALIGN); in tile_net_update()
944 gxio_mpipe_rules_add_channel(&rules, channel); in tile_net_update()
950 rc = gxio_mpipe_rules_commit(&rules); in tile_net_update()
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-arch.txt | 22 Your cpu_idle routines need to obey the following rules:
|
| /linux-4.1.27/Documentation/vm/ |
| D | overcommit-accounting | 49 The overcommit is based on the following rules
|
| D | hwpoison.txt | 27 * rules, as in get the standard locks, even if that means the
|
| /linux-4.1.27/net/ipv4/netfilter/ |
| D | Kconfig | 221 rules for simple packet filtering at local input, forwarding and
391 rules for simple ARP packet filtering at local input and
392 local output. On a bridge, you can also specify filtering rules
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | soc-camera.txt | 154 certain rules. E.g. if MEDIA_BUS_FMT_YUYV8_2X8 data is sampled with 8 bits per
160 host drivers can also provide their own conversion rules by implementing a
|
| D | v4l2-controls.txt | 20 The control framework was created in order to implement all the rules of the
|
| D | v4l2-framework.txt | 805 Users can setup udev rules that utilize the index attribute to make fancy
|
| /linux-4.1.27/Documentation/power/ |
| D | suspend-and-interrupts.txt | 119 First of all, if the IRQ is not shared, the rules for handling IRQF_NO_SUSPEND
121 directly at odds with the rules for handling system wakeup interrupts (interrupt
|
| D | basic-pm-debugging.txt | 110 you can carry out a binary search according to the rules:
|
| D | devices.txt | 285 and driver callbacks. To be precise, the following rules are used to determine
633 Some busses define rules about what different suspend states mean. PCI
|
| D | runtime_pm.txt | 61 If the subsystem chosen by applying the above rules doesn't provide the relevant
183 rules:
|
| /linux-4.1.27/fs/jffs2/ |
| D | README.Locking | 5 This document attempts to describe the existing locking rules for
67 No ordering rules have been made for doing so.
|
| /linux-4.1.27/Documentation/networking/mac80211_hwsim/ |
| D | README | 25 tests regardless of regulatory rules.
|
| /linux-4.1.27/tools/perf/Documentation/ |
| D | perf-probe.txt | 182 …ifying filter-out rule. You also can give several rules combined with "&" or "|", and fold those r…
|
| /linux-4.1.27/Documentation/kbuild/ |
| D | makefiles.txt | 63 scripts/Makefile.* common rules etc. for all kbuild Makefiles.
83 scripts/Makefile.* contains all the definitions/rules etc. that
367 Special rules are used when the kbuild infrastructure does
371 need special rules to prepare boot images etc.
373 Special rules are written as normal Make rules.
375 located, so all special rules shall provide a relative
378 Two variables are used when defining special rules:
713 the host programs in special rules must be prefixed with $(obj).
1048 There are no rules for naming architecture-specific targets,
|
| D | modules.txt | 273 named <filename>_shipped. When the kbuild rules kick in, a copy
285 files and the binary file, kbuild will pick up different rules
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | machinecheck | 53 normal kernel locking rules. The tolerance level configures
|
| /linux-4.1.27/security/integrity/ima/ |
| D | Kconfig | 45 Disabling this option will disregard LSM based policy rules.
|
| /linux-4.1.27/Documentation/ABI/ |
| D | README | 8 of stability according to the rules described below.
|
| /linux-4.1.27/sound/core/ |
| D | pcm_lib.c | 1156 if (constrs->rules) { in snd_pcm_hw_rule_add()
1157 memcpy(new, constrs->rules, in snd_pcm_hw_rule_add()
1159 kfree(constrs->rules); in snd_pcm_hw_rule_add()
1161 constrs->rules = new; in snd_pcm_hw_rule_add()
1164 c = &constrs->rules[constrs->rules_num]; in snd_pcm_hw_rule_add()
|
| D | pcm.c | 1016 kfree(runtime->hw_constraints.rules); in snd_pcm_detach_substream()
|
| D | pcm_native.c | 360 struct snd_pcm_hw_rule *r = &constrs->rules[k]; in snd_pcm_hw_refine()
|
| /linux-4.1.27/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 145 In this layered approach the following "rules" apply.
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | cxl.txt | 369 Udev rules
372 The following udev rules could be used to create a symlink to the
|
| /linux-4.1.27/Documentation/i2c/ |
| D | fault-codes | 34 Also, codes returned by adapter probe methods follow rules which are
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | cci.txt | 51 Definition: A standard property. Follow rules in the ePAPR for
|
| D | idle-states.txt | 260 rules ([5], 2.2.1 "Node names"), in particular state nodes which
|
| /linux-4.1.27/Documentation/trace/ |
| D | kprobetrace.txt | 81 You can write filtering rules of this event.
|
| /linux-4.1.27/Documentation/pcmcia/ |
| D | driver-changes.txt | 42 * New IRQ request rules (as of 2.6.35)
|
| /linux-4.1.27/Documentation/input/ |
| D | gamepad.txt | 68 Legacy drivers often don't comply to these rules. As we cannot change them
|
| /linux-4.1.27/drivers/net/vmxnet3/ |
| D | vmxnet3_ethtool.c | 577 u32 *rules) in vmxnet3_get_rxnfc() argument
|
| /linux-4.1.27/include/net/netfilter/ |
| D | nf_tables.h | 736 struct list_head rules; member
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | devres.txt | 12 4. Details : Life time rules, calling context, ...
|
| /linux-4.1.27/Documentation/spi/ |
| D | spi-summary | 321 Developer boards often play by different rules than product boards, and one
405 - Follow standard kernel rules, and provide DMA-safe buffers in
446 - I/O buffers use the usual Linux rules, and must be DMA-safe.
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | cpu-drivers.txt | 177 actual frequency must be determined using the following rules:
|
| /linux-4.1.27/net/ipv6/netfilter/ |
| D | Kconfig | 221 rules for simple packet filtering at local input, forwarding and
|
| /linux-4.1.27/drivers/xen/ |
| D | Kconfig | 52 Memory could be onlined automatically on domU by adding following line to udev rules:
|
| /linux-4.1.27/Documentation/s390/ |
| D | cds.txt | 76 interrupt handler according to the rules (flags) defined during I/O request
186 driver's interrupt handler as this is related to the rules (flags) defined
|
| /linux-4.1.27/Documentation/RCU/ |
| D | checklist.txt | 5 that make use of RCU. Violating any of the rules listed below will
211 srcu_read_unlock(), and with the same srcu_struct. The rules for
|
| D | listRCU.txt | 160 The system-call auditing code does not update auditing rules in place.
|
| D | rcu_dereference.txt | 9 Follow these rules to keep your RCU code working properly:
|
| D | whatisRCU.txt | 437 See checklist.txt for additional rules to follow when using RCU.
532 Again, see checklist.txt for additional rules governing the use of RCU.
|
| /linux-4.1.27/Documentation/acpi/ |
| D | namespace.txt | 229 The following rules apply when creating struct acpi_device objects on
|
| /linux-4.1.27/drivers/net/ethernet/chelsio/cxgb4/ |
| D | cxgb4_ethtool.c | 818 u32 *rules) in get_rxnfc() argument
|
| /linux-4.1.27/Documentation/sh/ |
| D | new-machine.txt | 93 board in arch/sh/boards/ and adding rules to hook your board in with the
|
| /linux-4.1.27/drivers/net/ethernet/intel/ixgbevf/ |
| D | ethtool.c | 798 u32 *rules __always_unused) in ixgbevf_get_rxnfc()
|
| /linux-4.1.27/include/sound/ |
| D | pcm.h | 240 struct snd_pcm_hw_rule *rules; member
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pcieaer-howto.txt | 160 pointers. AER driver follows the rules defined in
|
| D | MSI-HOWTO.txt | 47 the interrupt. PCI transaction ordering rules require that all the data
|
| /linux-4.1.27/Documentation/x86/ |
| D | intel_mpx.txt | 226 4. Special rules
|
| /linux-4.1.27/Documentation/ia64/ |
| D | fsys.txt | 160 needed. In other words, following the above rules yields extremely
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 125 IBM pSeries/iSeries pair, it was decided to enforce some strict rules
129 legacy iSeries platform breaks those rules as it predates this scheme,
134 required to use these rules as well.
817 specification enforces more strict rules. Nodes and properties should
|
| /linux-4.1.27/Documentation/scsi/ |
| D | scsi_eh.txt | 220 During recovery, the following rules are followed
|
| /linux-4.1.27/scripts/genksyms/ |
| D | parse.tab.c_shipped | 436 /* YYNRULES -- Number of rules. */
504 /* YYRHS -- A `-1'-separated list of the rules' RHS. */
|
| D | lex.lex.c_shipped | 219 * If so, '^' rules will be active on the next match, otherwise
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 5.Posting | 77 rules of thumb, however, which can help considerably:
|
| D | 4.Coding | 360 locking rules for data structures generally need to be explained somewhere.
|
| D | 2.Process | 313 the driver. Current rules require that drivers contributed to staging
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.tab.c_shipped | 426 /* YYNRULES -- Number of rules. */
492 /* YYRHS -- A `-1'-separated list of the rules' RHS. */
|
| D | zconf.lex.c_shipped | 238 * If so, '^' rules will be active on the next match, otherwise
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-parser.tab.c_shipped | 438 /* YYNRULES -- Number of rules. */
498 /* YYRHS -- A `-1'-separated list of the rules' RHS. */
|
| D | dtc-lexer.lex.c_shipped | 229 * If so, '^' rules will be active on the next match, otherwise
|
| /linux-4.1.27/Documentation/usb/ |
| D | gadget-testing.txt | 689 in each line. The rules stated above are best illustrated with an example:
|
| D | power-management.txt | 587 rules and require the attached child device and all descendants to be suspended.
|
| /linux-4.1.27/include/net/ |
| D | cfg80211.h | 2022 struct cfg80211_coalesce_rules *rules; member
|
| /linux-4.1.27/Documentation/arm64/ |
| D | arm-acpi.txt | 326 ACPI rules for such methods:
|
| /linux-4.1.27/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 607 processing rules).
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 347 To ensure that generic code follows the above rules, this
999 If a deadlock is impossible (i.e. the locking rules, as
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 306 general frowned upon as not playing by the agreed rules of the game. Such a
|
| /linux-4.1.27/drivers/net/wireless/mwifiex/ |
| D | cfg80211.c | 3105 ret = mwifiex_fill_coalesce_rule_info(priv, &coalesce->rules[i], in mwifiex_cfg80211_set_coalesce()
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | spkguide.txt | 1467 the collection, provided that you follow the rules of this License for
|
| /linux-4.1.27/drivers/net/ethernet/broadcom/ |
| D | tg3.c | 12540 u32 *rules __always_unused) in tg3_get_rxnfc()
|