Searched full:member (Results 1 – 25 of 163) sorted by relevance
1234567
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 53 containing four callback pointers, :c:member:`enable`, :c:member:`disable`,
54 :c:member:`select`, :c:member:`reflect`, a :c:member:`rating` field described
62 :c:member:`rating` field is greater than the value of that field for the
75 :c:member:`enable`
94 :c:member:`disable`
107 :c:member:`select`
118 :c:member:`states` array of struct cpuidle_state objects held by the
133 This callback is mandatory (i.e. the :c:member:`select` callback pointer
137 :c:member:`reflect`
154 :c:member:`exit_latency` value is greater than the number returned by that
[all …]
|
| D | devices.rst | 120 struct dev_pm_ops pointed to by the :c:member:`ops` member of
121 struct dev_pm_domain, or by the :c:member:`pm` member of struct bus_type,
147 The :c:member:`power.can_wakeup` flag just records whether the device (and its
150 :c:member:`power.wakeup` field is a pointer to an object of type
154 devices (i.e. devices whose :c:member:`can_wakeup` flags are set) and is created
164 :c:member:`power.wakeup` object exists for the given device and is created (or
176 :c:member:`power.wakeup` object exists and the corresponding :file:`power/wakeup`
199 runtime power management. This flag, :c:member:`runtime_auto`, is initialized
211 of the :c:member:`runtime_auto` flag by reading that file.
213 The device's :c:member:`runtime_auto` flag has no effect on the handling of
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | switch.rst | 26 session is connected to an eth port on a single member. Data to a LUN
28 stored on another member the I/O will be forwarded as required. This
30 dynamic, and the blocks stored on disk may be moved from member to
31 member as needed to balance the load.
40 sending data directly to the correct member.
51 Upper Tier - Determine which array member the I/O should be sent to.
52 Lower Tier - Load balance amongst paths to a particular member.
54 The lower tier consists of a single dm multipath device for each member.
56 the array member in one priority group, and leverages existing path
64 use 4 bits for each address range in a 16 member group (which is very
|
| D | unstriped.rst | 56 dd if=/dev/zero of=member-${i} bs=${MEMBER_SIZE} count=1 oflag=direct
57 losetup /dev/loop${i} member-${i}
68 diff /dev/mapper/set-${i} member-${i}
79 rm -f member-${i}
|
| /Documentation/doc-guide/ |
| D | kernel-doc.rst | 190 ``enum`` to describe unions or enums. ``member`` is used to mean struct
191 and union member names as well as enumerations in an enum.
194 lines, and ends with a member description, a blank comment line, or the
216 * @a: first member
217 * @b: second member
218 * @d: fourth member
238 * @memb1: first member of anonymous union/anonymous struct
239 * @memb2: second member of anonymous union/anonymous struct
240 * @memb3: third member of anonymous union/anonymous struct
241 * @memb4: fourth member of anonymous union/anonymous struct
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 25 spinlock_t lock; /* Example member */
103 return a single argument which is a pointer to a struct member in the
109 a pointer to a member by a simple subtraction using the offsetof() macro from
111 Notice that the contained member must not be a pointer, but an actual member
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | kernel-doc.rst | 207 * @memb1: first member of anonymous union/anonymous struct
208 * @memb2: second member of anonymous union/anonymous struct
209 * @memb3: third member of anonymous union/anonymous struct
210 * @memb4: fourth member of anonymous union/anonymous struct
214 * @bar.st1.memb1: first member of struct st1 on union bar
215 * @bar.st1.memb2: second member of struct st1 on union bar
216 * @bar.st2.memb1: first member of struct st2 on union bar
217 * @bar.st2.memb2: second member of struct st2 on union bar
349 ``&struct_name->member`` or ``&struct_name.member``
|
| /Documentation/translations/it_IT/doc-guide/ |
| D | kernel-doc.rst | 218 per descrivere unioni ed enumerati. ``member`` viene usato per indicare i
244 * @a: first member
245 * @b: second member
246 * @d: fourth member
266 * @memb1: first member of anonymous union/anonymous struct
267 * @memb2: second member of anonymous union/anonymous struct
268 * @memb3: third member of anonymous union/anonymous struct
269 * @memb4: fourth member of anonymous union/anonymous struct
273 * @bar.st1.memb1: first member of struct st1 on union bar
274 * @bar.st1.memb2: second member of struct st1 on union bar
[all …]
|
| /Documentation/driver-api/tty/ |
| D | tty_port.rst | 10 If the drivers implement :c:member:`tty_port.ops.activate()` and
11 :c:member:`tty_port.ops.shutdown()`, they can use tty_port_open(),
13 :c:member:`tty_struct.ops` hooks.
|
| D | tty_ldisc.rst | 58 Line discipline methods have access to :c:member:`tty_struct.flags` field. See
75 A caution: The :c:member:`tty_ldisc_ops.open()`,
76 :c:member:`tty_ldisc_ops.close()` and :c:member:`tty_driver.set_ldisc()`
|
| D | tty_driver.rst | 75 calling operations from :c:member:`tty_driver.ops`, see `TTY Operations
89 it. It must be known to the TTY layer at :c:member:`tty_driver.ops.install()`
98 :c:member:`tty_driver.ops.install` hook as a last resort. The last one is
|
| /Documentation/networking/devlink/ |
| D | etas_es58x.rst | 24 through ``ethtool -i`` as the first member of the
29 through ``ethtool -i`` as the second member of the
|
| /Documentation/kbuild/ |
| D | gendwarfksyms.rst | 297 "member base_type int byte_size(4) "
313 Perhaps the most common ABI compatible change is adding a member to a
329 reserved member needs a unique name, but as the actual purpose is usually
338 The reserved space can be taken into use by wrapping the member in a
339 union, which includes the original type and the replacement member::
350 of the first member of the union must start with `__kabi_reserved`. This
354 If we're replacing a member that doesn't follow this naming convention,
356 which we can do by changing the first union member's name to start with
360 simplify the process and also ensure the replacement member is correctly
382 member to a union where one of the fields has a name starting with
|
| /Documentation/userspace-api/netlink/ |
| D | intro.rst | 126 In Classic Netlink :c:member:`nlmsghdr.nlmsg_type` used to identify
130 identify the subsystem, and :c:member:`genlmsghdr.cmd` identifies
149 are initiated by the user. :c:member:`nlmsghdr.nlmsg_flags` should
155 :c:member:`nlmsghdr.nlmsg_seq` should be a set to a monotonically
160 :c:member:`nlmsghdr.nlmsg_seq` of ``0``.
162 :c:member:`nlmsghdr.nlmsg_pid` is the Netlink equivalent of an address.
166 The expected use for :c:member:`genlmsghdr.version` was to allow
176 As previously mentioned :c:member:`nlmsghdr.nlmsg_type` carries
219 is indicated by ``NLM_F_CAPPED`` in :c:member:`nlmsghdr.nlmsg_flags`.
224 :c:member:`nlmsghdr.nlmsg_flags`.
[all …]
|
| /Documentation/misc-devices/ |
| D | xilinx_sdfec.rst | 140 …- The ``state`` member of struct :c:type:`xsdfec_status <xsdfec_status>` filled by the ioctl :c:ma…
157 …- The ``code`` member of :c:type:`struct xsdfec_config <xsdfec_config>` filled by the ioctl :c:mac…
159 …- The ``state`` member of struct :c:type:`xsdfec_status <xsdfec_status>` filled by the ioctl :c:ma…
168 …- The ``code`` member of :c:type:`struct xsdfec_config <xsdfec_config>` filled by the ioctl :c:mac…
169 …- The ``state`` member of struct :c:type:`xsdfec_status <xsdfec_status>` filled by the ioctl :c:ma…
179 If the ``code`` member of :c:type:`struct xsdfec_config <xsdfec_config>` filled by the ioctl :c:mac…
188 …- The ``state`` member of :c:type:`struct xsdfec_status <xsdfec_status>` filled by the ioctl :c:ma…
208 …- For critical error the ``isr_err_count`` or ``uecc_count`` member of :c:type:`struct xsdfec_sta…
209 …- For non-critical errors the ``cecc_count`` member of :c:type:`struct xsdfec_stats <xsdfec_stats>…
|
| /Documentation/networking/ |
| D | radiotap-headers.rst | 23 of the it_present member of ieee80211_radiotap_header is set, it means that
34 we run out of space in the u32 it_present member, it is defined that b31 set
39 Note also that the it_len member __le16 is set to the total number of bytes
47 index whose matching bit is set in the it_present member of
|
| D | secid.rst | 9 The secid member in the flow structure is used in LSMs (e.g. SELinux) to indicate
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | cdev.rst | 118 ``response.data`` member. The ``response.length`` member must be set to the
126 via the ``flags`` member and the values correspond to the values found in
130 member (a negative errno value indicating failure). Note that failure
139 inside the IOCTL, but the request ``status`` member may still be negative in
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-write.rst | 57 ``EINVAL`` is returned. Set the desired scancode in the ``scancode`` member,
59 :c:type:`rc_proto`: member. All other members must be
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 7 may become inconsistent with data on other member disks. If the array is also
28 array member drives in the metadata area, on the parity drive of a particular
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-pisp-be.rst | 34 Global configuration data are passed to the ISP by populating the member of
45 Tiles parameters are passed to the ISP by populating the member of
|
| D | vidioc-enum-frameintervals.rst | 51 the `discrete` member is valid.
57 ``stepwise`` member is valid.
63 the union only the ``stepwise`` member is valid and the ``step``
|
| D | vidioc-enum-framesizes.rst | 52 ``discrete`` member is valid.
58 ``stepwise`` member is valid.
64 the union only the ``stepwise`` member is valid and the
|
| D | vidioc-g-fmt.rst | 51 the respective member of the ``fmt`` union. In case of video capture
55 member. When the requested buffer type is not supported drivers return
59 ``type`` field and all fields of the respective ``fmt`` union member.
|
| /Documentation/admin-guide/aoe/ |
| D | todo.rst | 13 the destructor member of the struct sk_buff is available to the aoe
|
1234567