Searched full:will (Results 126 – 150 of 18831) sorted by relevance
12345678910>>...754
| /linux-6.8/Documentation/staging/ |
| D | rpmsg.rst | 75 and its length (in bytes). The message will be sent on the specified
76 endpoint's channel, i.e. its source and destination address fields will be
80 In case there are no TX buffers available, the function will block until
99 The message will then be sent to the remote processor to which the
102 will be ignored).
104 In case there are no TX buffers available, the function will block until
124 The message will then be sent to the remote processor to which the
126 addresses will be ignored (and the user-provided addresses will
129 In case there are no TX buffers available, the function will block until
144 and its length (in bytes). The message will be sent on the specified
[all …]
|
| /linux-6.8/drivers/staging/media/atomisp/pci/ |
| D | ia_css_pipe_public.h | 10 * This program is distributed in the hope it will be useful, but WITHOUT
88 will OSYS receive, this resolution is equal to the output resolution of GDC
89 if not determined CSS will set output_system_in_res with main osys output pin resolution
104 then setting a zoom factor will have no effect.
110 /** Enabling BCI mode will cause yuv_scale binary to be picked up
149 * ~~~** DO NOT ADD NEW FIELD **~~~ This structure will be deprecated.
163 smaller than the input resolution, cropping will be performed by
164 the ISP. The first cropping that will be performed is on the upper
174 /** After an image pipe is created, this field will contain the info
177 /** After an image pipe is created, this field will contain the grid
[all …]
|
| /linux-6.8/Documentation/core-api/ |
| D | assoc_array.rst | 25 already in the array will replace the old object.
34 8. The array can iterated over. The objects will not necessarily come out in
40 problem, the iterator should lock against modification. Objects will not
76 preallocated metadata blocks that will be installed in the internal tree and
77 keeps track of the metadata blocks that will be removed from the tree when the
95 This will perform the edit functions, interpolating various write barriers
97 will then be passed to ``call_rcu()`` to free it and any dead stuff it points
127 *bit* position given by the level argument. The level argument will be a
189 If an object already exists for that key then it will be replaced with the
190 new object and the old one will be freed automatically.
[all …]
|
| D | symbol-namespaces.rst | 28 are required to import the namespace. Otherwise the kernel will, depending on
51 The corresponding ksymtab entry struct ``kernel_symbol`` will have the member
52 ``namespace`` set accordingly. A symbol that is exported without a namespace will
62 is been provided, that, if set, will become the default for all EXPORT_SYMBOL()
73 That will affect all EXPORT_SYMBOL() and EXPORT_SYMBOL_GPL() statements. A
74 symbol exported with EXPORT_SYMBOL_NS() while this definition is present, will
99 This will create a ``modinfo`` tag in the module for each imported namespace.
116 At module loading time (e.g. ``insmod``), the kernel will check each symbol
120 An error will be logged and loading will be failed with EINVAL. In order to
122 option is available: Setting MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS=y will
[all …]
|
| /linux-6.8/drivers/net/wireless/realtek/rtlwifi/ |
| D | Kconfig | 7 This option will enable support for the Realtek mac80211-based
24 If you choose to build it as a module, it will be called rtl8192ce
35 If you choose to build it as a module, it will be called rtl8192se
46 If you choose to build it as a module, it will be called rtl8192de
59 If you choose to build it as a module, it will be called rtl8723ae
72 If you choose to build it as a module, it will be called rtl8723be
83 If you choose to build it as a module, it will be called rtl8188ee
95 If you choose to build it as a module, it will be called rtl8192ee
107 If you choose to build it as a module, it will be called rtl8821ae
119 If you choose to build it as a module, it will be called rtl8192cu
|
| /linux-6.8/tools/testing/ktest/examples/include/ |
| D | min-config.conf | 10 # boot your machine, the closer the config you test with will be
16 # In this example, the final config will reside in
20 # The first test creates a MIN_CONFIG that will be the minimum
23 # The second test creates a MIN_CONFIG that will only boot
24 # the target and most likely will not let you ssh to it. (Notice
28 # The ${CONFIG_DIR}/config-skip (and -net) will hold the configs
32 # selected them. Sometimes it is possible that this file will hold
40 # modifying this config, ktest.pl will notice that the config-new-min(-net)
41 # exists, and will use that instead as the starting point.
44 # By using the OUTPUT_MIN_CONFIG as the starting point will allow ktest.pl to
|
| D | patchcheck.conf | 3 # This contains a test that takes two git commits and will test each
4 # commit between the two. The build test will look at what files the
6 # the build will fail.
12 # You can use a SHA1, a git tag, or anything that git will accept for a checkout
27 # Change PATCH_CHECKOUT to be the branch you want to test. The test will
40 # will be executed. Usually what is done is to ssh to the target box and
62 # If the variable CREATE_WARNINGS_FILE is set, this config will
64 # before running the patchcheck test, it will create the
83 # fifth patch, set PATCH_START1. This will make the first test start
86 # top config (the one you pass to ktest.pl), and this will use it,
[all …]
|
| /linux-6.8/Documentation/arch/riscv/ |
| D | uabi.rst | 17 #. All multi-letter extensions will be separated from other extensions by an
20 #. Additional standard extensions (starting with 'Z') will be sorted after
25 extension category. If multiple 'Z' extensions are named, they will be
29 #. Standard supervisor-level extensions (starting with 'S') will be listed
31 extensions are listed, they will be ordered alphabetically.
33 #. Standard machine-level extensions (starting with 'Zxm') will be listed
35 extensions are listed, they will be ordered alphabetically.
37 #. Non-standard extensions (starting with 'X') will be listed after all standard
38 extensions. If multiple non-standard extensions are listed, they will be
59 feature will be visible in guest VMs managed by this kernel.
|
| /linux-6.8/Documentation/RCU/ |
| D | stallwarn.rst | 36 with boot-time message rates, and will frequently result in
42 This message will include information on when the kthread last
45 which will include additional debugging information.
52 will eventually cause the system to run out of memory and hang.
58 This will prevent RCU callbacks from ever being invoked,
59 and in a CONFIG_PREEMPT_RCU kernel will further prevent
61 system will eventually run out of memory and hang. In the
97 which will include additional debugging information.
124 The offending function will usually be near the top of the stack.
127 is occurring, which will usually be in the function nearest the top of
[all …]
|
| /linux-6.8/Documentation/admin-guide/ |
| D | xfs.rst | 42 attributes) the on-disk superblock feature bit field will be
51 will reject the ``noattr2`` mount option if it is set.
86 inode creation to locations which will not result in inode
91 including those which will result in inode numbers occupying
103 ``st_blksize`` by **stat(2)** will be as small as possible to allow
109 ``swidth`` specified will return the ``swidth`` value (in bytes)
112 (in bytes) will be returned instead. Otherwise the behaviour
147 Data allocations will not be aligned at stripe unit
153 The filesystem will be mounted without running log recovery.
158 the mount will fail.
[all …]
|
| /linux-6.8/Documentation/ABI/testing/ |
| D | configfs-most | 31 configure type of data that will travel over
35 configure whether this link will be an input
43 configure the number of packets that will be
86 configure type of data that will travel over
90 configure whether this link will be an input
98 configure the number of packets that will be
141 configure type of data that will travel over
145 configure whether this link will be an input
153 configure the number of packets that will be
207 configure type of data that will travel over
[all …]
|
| /linux-6.8/include/linux/ |
| D | hwspinlock.h | 88 * required on a given setup, users will still work.
94 * Note: ERR_PTR(-ENODEV) will still be considered a success for NULL-checking
169 * @flags: a pointer to where the caller's interrupt state will be saved at
171 * This function attempts to lock the underlying hwspinlock, and will
192 * This function attempts to lock the underlying hwspinlock, and will
211 * This function attempts to lock an hwspinlock, and will immediately fail
215 * or spinlock to avoid dead-lock, that will let user can do some time-consuming
230 * This function attempts to lock an hwspinlock, and will immediately fail
247 * This function attempts to lock an hwspinlock, and will immediately fail
267 * @flags: a pointer to where the caller's interrupt state will be saved at
[all …]
|
| /linux-6.8/Documentation/admin-guide/device-mapper/ |
| D | thin-provisioning.rst | 36 cases will have different performance characteristics, for example due
53 directly. End users will be advised to use a higher-level volume
77 The amount of metadata you need will vary according to how many blocks
88 a warning will be issued and the excess space will not be used.
95 device when reloading is not forbidden at the moment, things will go
120 will be triggered which a userspace daemon should catch allowing it to
121 extend the pool device. Only one such event will be sent.
129 will trigger a dm event if free space on the metadata device drops below
136 If no such requests are made then commits will occur every second. This
141 If data space is exhausted the pool will either error or queue IO
[all …]
|
| /linux-6.8/tools/testing/selftests/tc-testing/ |
| D | README | 21 features. As new tests will be added, config options list will be updated.
28 In the current release, tdc run will abort due to a failure in setup or
30 because the kernel did not support a specific feature. (This will be
38 The path to the tc executable that will be most commonly tested can be defined
59 to tdc when starting a test run; the veth pair will still be created
62 Running tdc without any arguments will run all tests. Refer to the section
66 tdc will list the test names as they are being run, and print a summary in
68 output captured from the failing test will be printed immediately following
75 One run of tests is considered a "test suite" (this will be refined in the
96 Each of the commands in any stage will run in a shell instance.
[all …]
|
| /linux-6.8/drivers/gpu/drm/xe/ |
| D | Kconfig.profile | 5 Configures the default max job timeout after which job will
11 Configures the default min job timeout after which job will
32 HW will be reset to allow the more important context to execute.
38 will be forcefully taken away and higher priority context will
45 will be forcefully taken away and higher priority context will
53 and MAX values will apply when this configuration is enable to
|
| /linux-6.8/Documentation/filesystems/ |
| D | idmappings.rst | 6 Most filesystem developers will have encountered idmappings. They are used when
23 on, we will always prefix ids with ``u`` or ``k`` to make it clear whether
30 and write down the mappings it will generate::
41 Looking at this mathematically briefly will help us highlight some properties
80 third idmapping. The kernel will report unmapped ids as the overflowuid
84 need to verify that the range can contain our target id. We will skip this step
133 "userspace id" will be used to refer to the well known ``uid_t`` and ``gid_t``
134 types and "kernel id" will be used to refer to ``kuid_t`` and ``kgid_t``.
145 For the rest of this document we will prefix all userspace ids with ``u`` and
146 all kernel ids with ``k``. Ranges of idmappings will be prefixed with ``r``. So
[all …]
|
| D | debugfs.rst | 17 even debugfs interfaces are best designed with the idea that they will need
32 of business will be to create at least one directory to hold a set of
37 This call, if successful, will make a directory called name underneath the
38 indicated parent directory. If parent is NULL, the directory will be
44 of the functions described below will work.
54 should hold the file, data will be stored in the i_private field of the
58 the return value will be a dentry pointer to the created file,
109 As might be expected, this function will create a debugfs file to represent
126 A read on the resulting file will yield either Y (for non-zero values) or
127 N, followed by a newline. If written to, it will accept either upper- or
[all …]
|
| /linux-6.8/Documentation/process/ |
| D | 4.Coding.rst | 8 code. It is the code which will be examined by other developers and merged
10 will determine the ultimate success of the project.
12 This section will examine the coding process. We'll start with a look at a
14 will shift toward doing things right and the tools which can help in that
34 the standard; many developers will request that the code be reformatted
35 before they will even review it. A code base as large as the kernel
40 Occasionally, the kernel's coding style will run into conflict with an
41 employer's mandated style. In such cases, the kernel's style will have to
69 Some basic editor settings, such as indentation and line endings, will be
92 programmer's early expectation. Kernel developers will routinely submit
[all …]
|
| /linux-6.8/drivers/usb/misc/ |
| D | Kconfig | 34 module will be called uss720.
47 The module will be called audio. If you want to compile it as a
60 module will be called emi26.
69 will be called adutux.
77 module will be called usbsevseg.
87 The module will be called legousbtower. If you want to compile it as
100 module will be called usblcd.
113 module will be called cypress_cy7c63.
125 module will be called cytherm.
162 Say Y here if you want to control whether iOS devices will
[all …]
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-memory.json | 104 … channel. This counter is only useful with ECC DRAM devices. This count will increment one time …
164 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
173 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
182 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
191 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
200 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
209 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
218 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
227 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
252 … ranks are selected and are being throttled at the same time, the counter will only increment by 1…
[all …]
|
| /linux-6.8/drivers/char/ |
| D | Kconfig | 50 <file:Documentation/admin-guide/parport.rst>. The module will be called lp.
71 busy..) the kernel will stall until the printer is ready again.
92 module will be called ppdev.
106 /dev/vportNpn will be created when corresponding ports are
109 attribute called 'name' will be populated with a name for
127 will be created which exposes the operator panel display on IBM
156 times the button was pressed will be written to that device.
164 button; it will still execute a hard reset if the button is held
168 module will be called nwbutton.
170 Most people will answer Y to this question and "Reboot Using Button"
[all …]
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | floating-point.json | 11 …d double precision floating-point instructions retired; some instructions will count twice as note…
14 …d double precision floating-point instructions retired; some instructions will count twice as note…
19 …d single precision floating-point instructions retired; some instructions will count twice as note…
22 …d single precision floating-point instructions retired; some instructions will count twice as note…
27 …d double precision floating-point instructions retired; some instructions will count twice as note…
30 …d double precision floating-point instructions retired; some instructions will count twice as note…
35 …d single precision floating-point instructions retired; some instructions will count twice as note…
38 …d single precision floating-point instructions retired; some instructions will count twice as note…
43 …56-bit packed double precision FP instructions retired; some instructions will count twice as note…
46 … double precision floating-point instructions retired; some instructions will count twice as note…
[all …]
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/rocketlake/ |
| D | floating-point.json | 11 …d double precision floating-point instructions retired; some instructions will count twice as note…
14 …d double precision floating-point instructions retired; some instructions will count twice as note…
19 …d single precision floating-point instructions retired; some instructions will count twice as note…
22 …d single precision floating-point instructions retired; some instructions will count twice as note…
27 …d double precision floating-point instructions retired; some instructions will count twice as note…
30 …d double precision floating-point instructions retired; some instructions will count twice as note…
35 …d single precision floating-point instructions retired; some instructions will count twice as note…
38 …d single precision floating-point instructions retired; some instructions will count twice as note…
43 …56-bit packed double precision FP instructions retired; some instructions will count twice as note…
46 … double precision floating-point instructions retired; some instructions will count twice as note…
[all …]
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/icelake/ |
| D | floating-point.json | 11 …d double precision floating-point instructions retired; some instructions will count twice as note…
14 …d double precision floating-point instructions retired; some instructions will count twice as note…
19 …d single precision floating-point instructions retired; some instructions will count twice as note…
22 …d single precision floating-point instructions retired; some instructions will count twice as note…
27 …d double precision floating-point instructions retired; some instructions will count twice as note…
30 …d double precision floating-point instructions retired; some instructions will count twice as note…
35 …d single precision floating-point instructions retired; some instructions will count twice as note…
38 …d single precision floating-point instructions retired; some instructions will count twice as note…
43 …56-bit packed double precision FP instructions retired; some instructions will count twice as note…
46 … double precision floating-point instructions retired; some instructions will count twice as note…
[all …]
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | floating-point.json | 11 …d double precision floating-point instructions retired; some instructions will count twice as note…
14 …d double precision floating-point instructions retired; some instructions will count twice as note…
19 …d single precision floating-point instructions retired; some instructions will count twice as note…
22 …d single precision floating-point instructions retired; some instructions will count twice as note…
27 …d double precision floating-point instructions retired; some instructions will count twice as note…
30 …d double precision floating-point instructions retired; some instructions will count twice as note…
35 …d single precision floating-point instructions retired; some instructions will count twice as note…
38 …d single precision floating-point instructions retired; some instructions will count twice as note…
43 …56-bit packed double precision FP instructions retired; some instructions will count twice as note…
46 … double precision floating-point instructions retired; some instructions will count twice as note…
[all …]
|
12345678910>>...754