Home
last modified time | relevance | path

Searched refs:rules (Results 1 – 200 of 205) sorted by relevance

12

/linux-4.4.14/arch/tile/gxio/
Dmpipe.c223 void gxio_mpipe_rules_init(gxio_mpipe_rules_t *rules, in gxio_mpipe_rules_init() argument
226 rules->context = context; in gxio_mpipe_rules_init()
227 memset(&rules->list, 0, sizeof(rules->list)); in gxio_mpipe_rules_init()
232 int gxio_mpipe_rules_begin(gxio_mpipe_rules_t *rules, in gxio_mpipe_rules_begin() argument
239 gxio_mpipe_rules_list_t *list = &rules->list; in gxio_mpipe_rules_begin()
243 (gxio_mpipe_rules_rule_t *) (list->rules + list->head); in gxio_mpipe_rules_begin()
259 if (head + pad + sizeof(*rule) >= sizeof(list->rules)) in gxio_mpipe_rules_begin()
272 rule = (gxio_mpipe_rules_rule_t *) (list->rules + list->head); in gxio_mpipe_rules_begin()
285 stacks ? stacks->stacks[i] : rules->context->__stacks. in gxio_mpipe_rules_begin()
313 int gxio_mpipe_rules_add_channel(gxio_mpipe_rules_t *rules, in gxio_mpipe_rules_add_channel() argument
[all …]
/linux-4.4.14/Documentation/aoe/
Dudev.txt1 # 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
Dudev-install.sh27 rules_d=/etc/udev/rules.d
Daoe.txt29 udev configuration rules provided in udev.txt (in this directory).
32 rules on your system.
/linux-4.4.14/tools/perf/util/
Dstrfilter.c155 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()
174 const char *rules, const char **err) in strfilter__append() argument
179 if (!filter || !rules) in strfilter__append()
182 right = strfilter_node__new(rules, &ep); in strfilter__append()
202 int strfilter__or(struct strfilter *filter, const char *rules, const char **err) in strfilter__or() argument
204 return strfilter__append(filter, true, rules, err); in strfilter__or()
207 int strfilter__and(struct strfilter *filter, const char *rules, in strfilter__and() argument
210 return strfilter__append(filter, false, rules, err); in strfilter__and()
Dstrfilter.h29 struct strfilter *strfilter__new(const char *rules, const char **err);
42 const char *rules, const char **err);
55 const char *rules, const char **err);
/linux-4.4.14/net/wireless/
Dgenregdb.awk24 rules = 0;
120 rules++
127 printf "\t.n_reg_rules = %d\n", rules
129 rules = 0;
Ddb.txt12 # regulatory rules that cover the regulatory domains you will be using. Your
DKconfig156 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.
Dnl80211.c9532 rule = &rdev->coalesce->rules[i]; in nl80211_send_coalesce_rules()
9608 rule = &coalesce->rules[i]; in cfg80211_rdev_free_coalesce()
9613 kfree(coalesce->rules); in cfg80211_rdev_free_coalesce()
9732 new_coalesce.rules = kcalloc(n_rules, sizeof(new_coalesce.rules[0]), in nl80211_set_coalesce()
9734 if (!new_coalesce.rules) in nl80211_set_coalesce()
9743 &new_coalesce.rules[i]); in nl80211_set_coalesce()
9765 tmp_rule = &new_coalesce.rules[i]; in nl80211_set_coalesce()
9770 kfree(new_coalesce.rules); in nl80211_set_coalesce()
/linux-4.4.14/security/smack/
DKconfig16 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.4.14/kernel/
Daudit_watch.c54 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()
289 list_for_each_entry_safe(r, nextr, &owatch->rules, rlist) { in audit_update_watch()
310 list_add(&nentry->rule.rlist, &nwatch->rules); in audit_update_watch()
344 list_for_each_entry_safe(r, nextr, &w->rules, rlist) { in audit_remove_parent_watches()
409 list_add(&krule->rlist, &watch->rules); in audit_add_to_parent()
458 if (list_empty(&watch->rules)) { in audit_remove_watch_rule()
Daudit_tree.c16 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()
563 if (list_empty(&tree->rules) && !tree->goner) { in audit_remove_tree_rule()
721 list_add(&rule->rlist, &tree->rules); in audit_add_tree_rule()
727 list_add(&rule->rlist, &tree->rules); in audit_add_tree_rule()
774 list_del_init(&tree->rules); in audit_add_tree_rule()
/linux-4.4.14/Documentation/dvb/
Dudev.txt8 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.4.14/net/ceph/crush/
Dcrush.c126 if (map->rules) { in crush_destroy()
129 crush_destroy_rule(map->rules[b]); in crush_destroy()
130 kfree(map->rules); in crush_destroy()
Dmapper.c45 if (map->rules[i] && in crush_find_rule()
46 map->rules[i]->mask.ruleset == ruleset && in crush_find_rule()
47 map->rules[i]->mask.type == type && in crush_find_rule()
48 map->rules[i]->mask.min_size <= size && in crush_find_rule()
49 map->rules[i]->mask.max_size >= size) in crush_find_rule()
825 rule = map->rules[ruleno]; in crush_do_rule()
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-block-dm7 Users: util-linux, device-mapper udev rules
16 Users: util-linux, device-mapper udev rules
25 Users: util-linux, device-mapper udev rules
Dsysfs-bus-platform13 matching rules binding. Writing to driver_override does not
Dsysfs-bus-amba12 This returns the device to standard matching rules binding.
Dima_policy11 by opening the file, writing the rules one at a time and
Dsysfs-bus-pci275 This returns the device to standard matching rules binding.
/linux-4.4.14/Documentation/filesystems/
Ddirectory-locking11 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
DLocking1 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 …]
Dgfs2-glocks.txt1 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:
D00-INDEX4 - info on locking rules as they pertain to Linux VFS.
73 - info on the Global File System 2 - Glock internal locking rules.
Dfiles.txt33 appear atomic. Here are the locking rules for
Ddebugfs.txt5 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
Dporting332 .d_compare() calling convention and locking rules are significantly
339 .d_hash() calling convention and locking rules are significantly
Dmandatory-locking.txt59 to entire files, so the mandatory locking rules also have byte level
Dvfs.txt981 Same locking and synchronisation rules as d_compare regarding
1139 to show all the currently active options. The rules are:
1150 from the above rules.
1152 The underlying reason for the above rules is to make sure, that a
Dseq_file.txt73 itself. A seq_file implementation that is formatting firewall rules, for
/linux-4.4.14/security/apparmor/include/
Dfile.h183 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.4.14/Documentation/networking/
Dtc-actions-env-rules.txt2 The "environmental" rules for authors of any new tc actions are:
17 The "environmental" rules for callers of actions (qdiscs etc) are:
Dpolicy-routing.txt12 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.
Dvrf.txt3 The VRF device combined with ip rules provides the ability to create virtual
14 the use of higher priority ip rules (Policy Based Routing, PBR) to take
15 precedence over the VRF device rules directing specific traffic as desired.
41 the VRF device. Similarly on egress routing rules are used to send packets
44 VRF as a whole.[1] Similiarly, netfilter [2] and tc rules can be applied
45 using the VRF device to specify rules that apply to the VRF domain as a whole.
108 Remember to add the ip rules as well:
114 Without the rules route lookups are not directed to the table.
320 # add rules that direct lookups to vrf table
Dnetdevices.txt10 struct net_device allocation rules
48 struct net_device synchronization rules
98 struct napi_struct synchronization rules
Dopenvswitch.txt151 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:
Dregulatory.txt38 # Example file, should be put in /etc/udev/rules.d/regulatory.rules
197 rules built into the kernel itself may be desirable. To account
Dtproxy.txt55 add rules like this to the iptables ruleset above:
D00-INDEX203 tc-actions-env-rules.txt
204 - rules for traffic control (tc) actions.
Dipvs-sysctl.txt54 also handled by stateful firewall rules. That is, iptables rules
Doperstates.txt19 and changeable from userspace under certain rules.
Dnetdev-features.txt138 protect against other callbacks (the rules you need to find out).
Dnetdev-FAQ.txt145 Before you jump to go do the above, do note that the normal stable rules
Dswitchdev.txt95 Udev rules should be used for port netdev naming, using some unique attribute
Dscaling.txt289 CPU. These rules aim to ensure that a flow only moves to a new CPU when
/linux-4.4.14/arch/tile/include/gxio/
Dmpipe.h956 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.4.14/Documentation/trace/
Dstm.txt24 mechanism via configfs, that allows defining rules that map string
25 identifiers to ranges of masters and channels. If these rules (policy)
29 This policy is a tree structure containing rules (policy_node) that
50 These rules can be nested, for example, one can define a rule "dummy"
Dkprobetrace.txt81 You can write filtering rules of this event.
/linux-4.4.14/tools/power/acpi/tools/ec/
DMakefile17 include ../../Makefile.rules
/linux-4.4.14/Documentation/arm/
Dkernel_mode_neon.txt54 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:
Dcluster-pm-race-avoidance.txt487 rules for the intermediate (non-outermost) cluster levels.
/linux-4.4.14/arch/um/os-Linux/skas/
DMakefile10 include arch/um/scripts/Makefile.rules
/linux-4.4.14/fs/hostfs/
DMakefile11 include arch/um/scripts/Makefile.rules
/linux-4.4.14/arch/x86/um/os-Linux/
DMakefile13 include arch/um/scripts/Makefile.rules
/linux-4.4.14/arch/um/kernel/skas/
DMakefile15 include arch/um/scripts/Makefile.rules
/linux-4.4.14/arch/um/os-Linux/drivers/
DMakefile13 include arch/um/scripts/Makefile.rules
/linux-4.4.14/Documentation/security/
DSmack.txt43 smackctl - load the Smack access rules
134 This interface allows modification of existing access control rules.
181 This interface allows access control rules in addition to
182 the system defined rules to be specified. The format accepted
193 This interface allows access control rules in addition to
194 the system defined rules to be specified. The format accepted
206 This interface allows process specific access rules to be
207 defined. These rules are only consulted if access would
212 This interface allows process specific access rules to be
213 defined. These rules are only consulted if access would
[all …]
Dcredentials.txt108 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.4.14/Documentation/devicetree/bindings/iio/dac/
Dti,dac7512.txt7 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt
/linux-4.4.14/drivers/staging/lustre/lustre/ptlrpc/
Dsec_config.c233 struct sptlrpc_rule *rules; in sptlrpc_rule_set_expand() local
244 rules = kcalloc(nslot, sizeof(*rset->srs_rules), GFP_NOFS); in sptlrpc_rule_set_expand()
245 if (rules == NULL) in sptlrpc_rule_set_expand()
250 memcpy(rules, rset->srs_rules, in sptlrpc_rule_set_expand()
256 rset->srs_rules = rules; in sptlrpc_rule_set_expand()
/linux-4.4.14/Documentation/locking/
Dlockdep-design.txt13 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
Dmutex-design.txt89 The mutex subsystem checks and enforces the following rules:
/linux-4.4.14/drivers/usb/serial/
DMakefile-keyspan_pda_fw2 # some rules to handle the quirks of the 'as31' assembler, like
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-devices2 # is documented in Documentation/sysfs-rules.txt
Dsysfs-bus-firewire38 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.4.14/Documentation/devicetree/bindings/display/panel/
Dlg,lg4573.txt7 The panel must obey rules for SPI slave device specified in document [1].
Dsamsung,ld9040.txt11 The panel must obey rules for SPI slave device specified in document [2].
/linux-4.4.14/Documentation/sound/alsa/soc/
Dpops_clicks.txt22 shutdown and follows some basic rules:-
36 ADC until all the pops have occurred. This follows similar power rules to
/linux-4.4.14/
DKbuild42 # We use internal kbuild rules to avoid the "is up to date" message from make
77 # We use internal kbuild rules to avoid the "is up to date" message from make
D.gitignore10 # Normal rules
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.quirks40 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.4.14/tools/power/acpi/tools/acpidump/
DMakefile48 include ../../Makefile.rules
/linux-4.4.14/arch/um/os-Linux/
DMakefile20 include arch/um/scripts/Makefile.rules
/linux-4.4.14/net/netfilter/
Dnf_tables_core.c127 rule = list_entry(&chain->rules, struct nft_rule, list); in nft_do_chain()
130 list_for_each_entry_continue_rcu(rule, &chain->rules, list) { in nft_do_chain()
Dnf_tables_api.c316 list_for_each_entry(rule, &ctx->chain->rules, list) { in nft_delrule_by_chain()
1453 INIT_LIST_HEAD(&chain->rules); in nf_tables_newchain()
1756 list_for_each_entry(rule, &chain->rules, list) { in __nf_tables_rule_lookup()
1816 if ((event != NFT_MSG_DELRULE) && (rule->list.prev != &chain->rules)) { in nf_tables_fill_rule_info()
1902 list_for_each_entry_rcu(rule, &chain->rules, list) { in nf_tables_dump_rules()
2148 list_add_tail_rcu(&rule->list, &chain->rules); in nf_tables_newrule()
2153 list_add_rcu(&rule->list, &chain->rules); in nf_tables_newrule()
4200 list_for_each_entry(rule, &chain->rules, list) { in nf_tables_check_loops()
DKconfig587 The target allows you to create rules in the "mangle" table which alter
704 It also adds the "TOS" target, which allows you to create rules in
732 The target allows you to create rules in the "raw" and "mangle" tables
783 This option adds a `LOG' target, which allows you to create rules in
891 For it to work you will have to configure certain iptables rules
904 the tables, chains, rules.
/linux-4.4.14/tools/build/Documentation/
DBuild.txt126 The build framework provides standard compilation rules to handle .S and .c
152 - Dependency rules generated by 'gcc -Wp,-MD,...'
159 Single rules
/linux-4.4.14/net/bridge/netfilter/
DKconfig44 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.4.14/arch/um/kernel/
DMakefile26 include arch/um/scripts/Makefile.rules
/linux-4.4.14/arch/x86/um/
DMakefile45 include arch/um/scripts/Makefile.rules
/linux-4.4.14/drivers/net/ethernet/broadcom/bnx2x/
Dbnx2x_sp.c890 union eth_classify_rule_cmd *rule_entry = &data->rules[rule_idx]; in bnx2x_set_one_mac_e2()
1074 union eth_classify_rule_cmd *rule_entry = &data->rules[rule_idx]; in bnx2x_set_one_vlan_e2()
1124 union eth_classify_rule_cmd *rule_entry = &data->rules[rule_idx]; in bnx2x_set_one_vlan_mac_e2()
2458 data->rules[rule_idx].client_id = p->cl_id; in bnx2x_set_rx_mode_e2()
2459 data->rules[rule_idx].func_id = p->func_id; in bnx2x_set_rx_mode_e2()
2461 data->rules[rule_idx].cmd_general_data = in bnx2x_set_rx_mode_e2()
2465 &(data->rules[rule_idx++]), in bnx2x_set_rx_mode_e2()
2471 data->rules[rule_idx].client_id = p->cl_id; in bnx2x_set_rx_mode_e2()
2472 data->rules[rule_idx].func_id = p->func_id; in bnx2x_set_rx_mode_e2()
2474 data->rules[rule_idx].cmd_general_data = in bnx2x_set_rx_mode_e2()
[all …]
Dbnx2x_hsi.h3896 union eth_classify_rule_cmd rules[CLASSIFY_RULES_COUNT]; member
4069 struct eth_filter_rules_cmd rules[FILTER_RULES_COUNT]; member
4085 union eth_classify_rule_cmd rules[CLASSIFY_RULES_COUNT]; member
4171 struct eth_multicast_rules_cmd rules[MULTICAST_RULES_COUNT]; member
Dbnx2x_ethtool.c3304 u32 *rules __always_unused) in bnx2x_get_rxnfc()
/linux-4.4.14/include/linux/crush/
Dcrush.h183 struct crush_rule **rules; member
/linux-4.4.14/arch/tile/include/hv/
Ddrv_mpipe_intf.h573 uint8_t rules[4096 - 4]; member
/linux-4.4.14/Documentation/isdn/
DREADME.diversion56 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.4.14/drivers/staging/media/bcm2048/
DTODO17 rules, and do evil tricks, like returning from a function inside a
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dhi6220-clock.txt4 please refer the following document to know more about the binding rules
/linux-4.4.14/scripts/coccinelle/null/
Dderef_null.cocci25 // 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.4.14/net/core/
Dfib_rules.c720 static void attach_rules(struct list_head *rules, struct net_device *dev) in attach_rules() argument
724 list_for_each_entry(rule, rules, list) { in attach_rules()
734 static void detach_rules(struct list_head *rules, struct net_device *dev) in detach_rules() argument
738 list_for_each_entry(rule, rules, list) { in detach_rules()
/linux-4.4.14/Documentation/
Dsysfs-rules.txt11 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
Dkselftest.txt76 In general, the rules for for selftests are
Dstable_kernel_rules.txt26 - It must follow the Documentation/SubmittingPatches rules.
57 Send the patch, after verifying that it follows the above rules, to
DManagementStyle10 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
Dvolatile-considered-harmful.txt32 If all the code follows the locking rules, the value of shared_data cannot
DHOWTO99 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
Dpi-futex.txt14 abstraction, with strict rules that keep the implementation
DSubmittingDrivers42 The same rules apply as 2.4 except that you should follow linux-kernel
Dkref.txt33 rules:
D00-INDEX425 - rules and procedures for the -stable kernel releases.
430 sysfs-rules.txt
Dprintk-formats.txt108 The conversion rules are applied according to an optional combination
Dcpu-hotplug.txt97 no locking rules as of now. Typical usage is to init topology during boot,
Dbcache.txt49 bcache-tools now ships udev rules, and bcache devices are known to the kernel
DSubmittingPatches320 Trivial patches must qualify for one of the following rules:
419 pass it on as an open-source patch. The rules are pretty simple: if you
DDMA-API-HOWTO.txt113 set of rules regarding this, and this text is an attempt to finally
DCodingStyle341 EVER use a typedef unless you can clearly match one of those rules.
Dmemory-barriers.txt2467 address register if ordering rules are sufficiently relaxed:
2472 If ordering rules are relaxed, it must be assumed that accesses done inside an
/linux-4.4.14/arch/um/drivers/
DMakefile67 include arch/um/scripts/Makefile.rules
/linux-4.4.14/scripts/coccinelle/api/alloc/
Dkzalloc-simple.cocci11 // URL: http://coccinelle.lip6.fr/rules/kzalloc.html
/linux-4.4.14/Documentation/cgroups/
Ddevices.txt115 For every propagated exception, the effective rules will be re-evaluated based
116 on current parent's access rules.
Dblkio-controller.txt152 - 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
Dcpusets.txt205 The following rules apply to each cpuset:
211 These rules, and the natural hierarchy of cpusets, enable efficient
Dunified-hierarchy.txt230 enabled, tasks are always only on the leaves. This rules out
/linux-4.4.14/Documentation/devicetree/bindings/
DABI.txt18 II. General binding rules
Dsubmitting-patches.txt6 0) Normal patch submission rules from Documentation/SubmittingPatches
/linux-4.4.14/drivers/thermal/ti-soc-thermal/
DKconfig19 This includes trip points definitions, extrapolation rules and
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-ocores.txt24 frequency. So the following rules are set to fix this situation:
Di2c-arb-gpio-challenge.txt7 the standard I2C multi-master rules. Using GPIOs is generally useful in
/linux-4.4.14/net/openvswitch/
DKconfig26 translate it into packet processing rules.
/linux-4.4.14/net/ceph/
Dosdmap.c192 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.4.14/net/bridge/
DKconfig27 take this into account when setting up your firewall rules.
/linux-4.4.14/scripts/package/
Dbuilddeb410 cat <<EOF > debian/rules
428 tar caf ../${sourcename}_${packageversion}.debian.tar.gz debian/{copyright,rules,changelog,control}
/linux-4.4.14/drivers/net/ethernet/tile/
Dtilegx.c925 static gxio_mpipe_rules_t rules; /* too big to fit on the stack */ in tile_net_update() local
934 gxio_mpipe_rules_init(&rules, &md->context); in tile_net_update()
941 gxio_mpipe_rules_begin(&rules, md->first_bucket, in tile_net_update()
943 gxio_mpipe_rules_set_headroom(&rules, NET_IP_ALIGN); in tile_net_update()
945 gxio_mpipe_rules_add_channel(&rules, channel); in tile_net_update()
951 rc = gxio_mpipe_rules_commit(&rules); in tile_net_update()
/linux-4.4.14/Documentation/vm/
Dovercommit-accounting49 The overcommit is based on the following rules
Dhwpoison.txt27 * rules, as in get the standard locks, even if that means the
/linux-4.4.14/Documentation/scheduler/
Dsched-arch.txt22 Your cpu_idle routines need to obey the following rules:
/linux-4.4.14/Documentation/power/
Dsuspend-and-interrupts.txt119 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
Dbasic-pm-debugging.txt110 you can carry out a binary search according to the rules:
Ddevices.txt285 and driver callbacks. To be precise, the following rules are used to determine
640 Some busses define rules about what different suspend states mean. PCI
Druntime_pm.txt61 If the subsystem chosen by applying the above rules doesn't provide the relevant
183 rules:
/linux-4.4.14/Documentation/video4linux/
Dsoc-camera.txt154 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
Dv4l2-controls.txt20 The control framework was created in order to implement all the rules of the
Dv4l2-framework.txt805 Users can setup udev rules that utilize the index attribute to make fancy
/linux-4.4.14/fs/jffs2/
DREADME.Locking5 This document attempts to describe the existing locking rules for
67 No ordering rules have been made for doing so.
/linux-4.4.14/net/ipv4/netfilter/
DKconfig236 rules for simple packet filtering at local input, forwarding and
406 rules for simple ARP packet filtering at local input and
407 local output. On a bridge, you can also specify filtering rules
/linux-4.4.14/Documentation/networking/mac80211_hwsim/
DREADME25 tests regardless of regulatory rules.
/linux-4.4.14/Documentation/kbuild/
Dmakefiles.txt63 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,
Dmodules.txt273 named <filename>_shipped. When the kbuild rules kick in, a copy
285 files and the binary file, kbuild will pick up different rules
Dkconfig-language.txt542 formula extracted from CPP #ifdefs and build-rules into a SAT solver in order
/linux-4.4.14/Documentation/x86/x86_64/
Dmachinecheck53 normal kernel locking rules. The tolerance level configures
/linux-4.4.14/security/integrity/ima/
DKconfig45 Disabling this option will disregard LSM based policy rules.
/linux-4.4.14/tools/perf/Documentation/
Dperf-probe.txt189 …ifying filter-out rule. You also can give several rules combined with "&" or "|", and fold those r…
/linux-4.4.14/Documentation/ABI/
DREADME8 of stability according to the rules described below.
/linux-4.4.14/sound/core/
Dpcm_lib.c1157 if (constrs->rules) { in snd_pcm_hw_rule_add()
1158 memcpy(new, constrs->rules, in snd_pcm_hw_rule_add()
1160 kfree(constrs->rules); in snd_pcm_hw_rule_add()
1162 constrs->rules = new; in snd_pcm_hw_rule_add()
1165 c = &constrs->rules[constrs->rules_num]; in snd_pcm_hw_rule_add()
Dpcm.c1016 kfree(runtime->hw_constraints.rules); in snd_pcm_detach_substream()
Dpcm_native.c360 struct snd_pcm_hw_rule *r = &constrs->rules[k]; in snd_pcm_hw_refine()
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dfsl-tsec-phy.txt63 certain packet types (user) defined by filer rules to wake up the system.
/linux-4.4.14/Documentation/RCU/
DarrayRCU.txt18 integers, which means that the rules governing handling of these indexes
Dchecklist.txt5 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
DlistRCU.txt160 The system-call auditing code does not update auditing rules in place.
Drcu_dereference.txt9 Follow these rules to keep your RCU code working properly:
DwhatisRCU.txt439 See checklist.txt for additional rules to follow when using RCU.
534 Again, see checklist.txt for additional rules governing the use of RCU.
/linux-4.4.14/Documentation/networking/caif/
DLinux-CAIF.txt145 In this layered approach the following "rules" apply.
/linux-4.4.14/Documentation/powerpc/
Dcxl.txt373 Udev rules
376 The following udev rules could be used to create a symlink to the
/linux-4.4.14/Documentation/i2c/
Dfault-codes34 Also, codes returned by adapter probe methods follow rules which are
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dcci.txt52 Definition: A standard property. Follow rules in the ePAPR for
Didle-states.txt260 rules ([5], 2.2.1 "Node names"), in particular state nodes which
/linux-4.4.14/Documentation/pcmcia/
Ddriver-changes.txt42 * New IRQ request rules (as of 2.6.35)
/linux-4.4.14/Documentation/input/
Dgamepad.txt68 Legacy drivers often don't comply to these rules. As we cannot change them
/linux-4.4.14/Documentation/driver-model/
Ddevres.txt12 4. Details : Life time rules, calling context, ...
/linux-4.4.14/Documentation/spi/
Dspi-summary321 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.4.14/include/net/netfilter/
Dnf_tables.h749 struct list_head rules; member
/linux-4.4.14/drivers/net/ethernet/cavium/thunder/
Dnicvf_ethtool.c451 struct ethtool_rxnfc *info, u32 *rules) in nicvf_get_rxnfc() argument
/linux-4.4.14/drivers/net/vmxnet3/
Dvmxnet3_ethtool.c635 u32 *rules) in vmxnet3_get_rxnfc() argument
/linux-4.4.14/Documentation/cpu-freq/
Dcpu-drivers.txt177 actual frequency must be determined using the following rules:
/linux-4.4.14/net/ipv6/netfilter/
DKconfig236 rules for simple packet filtering at local input, forwarding and
/linux-4.4.14/drivers/xen/
DKconfig52 Memory could be onlined automatically on domU by adding following line to udev rules:
/linux-4.4.14/Documentation/s390/
Dcds.txt76 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.4.14/Documentation/acpi/
Dnamespace.txt229 The following rules apply when creating struct acpi_device objects on
/linux-4.4.14/drivers/net/ethernet/intel/ixgbevf/
Dethtool.c798 u32 *rules __always_unused) in ixgbevf_get_rxnfc()
/linux-4.4.14/Documentation/sh/
Dnew-machine.txt93 board in arch/sh/boards/ and adding rules to hook your board in with the
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt204 number). The reconstruction rules/steps are simple:
/linux-4.4.14/Documentation/x86/
Dintel_mpx.txt226 4. Special rules
/linux-4.4.14/Documentation/PCI/
Dpcieaer-howto.txt160 pointers. AER driver follows the rules defined in
DMSI-HOWTO.txt47 the interrupt. PCI transaction ordering rules require that all the data
/linux-4.4.14/include/sound/
Dpcm.h241 struct snd_pcm_hw_rule *rules; member
/linux-4.4.14/Documentation/ia64/
Dfsys.txt160 needed. In other words, following the above rules yields extremely
/linux-4.4.14/Documentation/DocBook/
Dalsa-driver-api.xml.db179 API-snd-ac97-pcm-double-rate-rules
Dkernel-api.xml.db587 API-audit-list-rules-send
/linux-4.4.14/drivers/net/ethernet/chelsio/cxgb4/
Dcxgb4_ethtool.c1033 u32 *rules) in get_rxnfc() argument
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt125 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.4.14/Documentation/scsi/
Dscsi_eh.txt220 During recovery, the following rules are followed
/linux-4.4.14/scripts/genksyms/
Dparse.tab.c_shipped448 /* YYNRULES -- Number of rules. */
516 /* YYRHS -- A `-1'-separated list of the rules' RHS. */
Dlex.lex.c_shipped219 * If so, '^' rules will be active on the next match, otherwise
/linux-4.4.14/Documentation/development-process/
D5.Posting77 rules of thumb, however, which can help considerably:
D4.Coding360 locking rules for data structures generally need to be explained somewhere.
D2.Process313 the driver. Current rules require that drivers contributed to staging
/linux-4.4.14/scripts/kconfig/
Dzconf.tab.c_shipped439 /* YYNRULES -- Number of rules. */
506 /* YYRHS -- A `-1'-separated list of the rules' RHS. */
Dzconf.lex.c_shipped247 * If so, '^' rules will be active on the next match, otherwise
/linux-4.4.14/Documentation/usb/
Dgadget-testing.txt687 in each line. The rules stated above are best illustrated with an example:
Dpower-management.txt599 rules and require the attached child device and all descendants to be suspended.
/linux-4.4.14/include/net/
Dcfg80211.h2063 struct cfg80211_coalesce_rules *rules; member
/linux-4.4.14/Documentation/arm64/
Darm-acpi.txt326 ACPI rules for such methods:
/linux-4.4.14/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt607 processing rules).
/linux-4.4.14/lib/
DKconfig.debug357 To ensure that generic code follows the above rules, this
1008 If a deadlock is impossible (i.e. the locking rules, as
/linux-4.4.14/Documentation/virtual/kvm/
Dtimekeeping.txt306 general frowned upon as not playing by the agreed rules of the game. Such a
/linux-4.4.14/scripts/dtc/
Ddtc-lexer.lex.c_shipped230 * If so, '^' rules will be active on the next match, otherwise
Ddtc-parser.tab.c_shipped445 /* YYNRULES -- Number of rules. */
/linux-4.4.14/drivers/net/wireless/mwifiex/
Dcfg80211.c3272 ret = mwifiex_fill_coalesce_rule_info(priv, &coalesce->rules[i], in mwifiex_cfg80211_set_coalesce()

12