| /linux/drivers/macintosh/ |
| H A D | windfarm_pid.h | 25 * but could be implemented (with necessary adjustment of the history
30 int history_len; /* Size of history buffer */
41 s32 samples[WF_PID_MAX_HISTORY]; /* samples history buffer */
42 s32 errors[WF_PID_MAX_HISTORY]; /* error history buffer */
59 * but could be implemented (with necessary adjustment of the history
64 int history_len; /* Size of history buffer */
78 s32 powers[WF_PID_MAX_HISTORY]; /* power history buffer */
79 s32 errors[WF_PID_MAX_HISTORY]; /* error history buffer */
80 s32 temps[2]; /* temp. history buffer */
|
| H A D | windfarm_pm121.c | 99 * History = 2 entries
109 * History = 2 entries
121 * History = 2 entries
131 * History = 2 entries
143 * History = 2 entries
153 * History = 2 entries
165 * History = 2 entries
175 * History = 2 entries
681 printk(KERN_WARNING "pm121: History size overflow on " in pm121_create_cpu_fans()
|
| /linux/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 17 development history. Indeed, given the scale of the project, avoiding
25 "Rebasing" is the process of changing the history of a series of commits
36 - Changing the history of a set of patches by fixing (or deleting) broken
39 type of operation will be referred to as "history modification"
43 history; used improperly, it can obscure that history and introduce bugs.
48 - History that has been exposed to the world beyond your private system
61 - Do not rebase a branch that contains history created by others. If you
63 custodian of their history. You should not change it. With few
65 explicitly reverted rather than disappeared via history modification.
78 - Realize that reparenting a patch series (or making significant history
[all …]
|
| H A D | messy-diffstat.rst | 11 complicated development history will yield a massive diffstat containing a
20 A Git development history proceeds as a series of commits. In a simplified
30 Here, there are two clear points in the history; Git will essentially
36 result in the simplest case is a history that looks like::
46 consider a slightly more complex development history::
|
| /linux/Documentation/process/ |
| H A D | 7.AdvancedTopics.rst | 41 of the mainline repository, explore the revision history, commit changes to
43 rewriting of history (such as rebase) is also useful. Git comes with its
70 development history. An inconvenient patch (one which breaks bisection,
72 made to disappear from the history entirely. A patch series can be
76 ability to revise history can help in the creation of clean patch sets with
80 a simple obsession for the creation of the perfect project history.
81 Rewriting history will rewrite the changes contained in that history,
84 view of the project history; if you rewrite history which other developers
86 for those developers. So a simple rule of thumb applies here: history
93 (i.e. changes which do not share the same history). It is possible to
[all …]
|
| /linux/drivers/acpi/acpica/ |
| H A D | dbhistry.c | 4 * Module Name: dbhistry - debugger HISTORY command
39 * DESCRIPTION: Add a command line to the history buffer.
108 * DESCRIPTION: Display the contents of the history buffer
119 /* Dump entire history buffer */ in acpi_db_display_history()
146 * DESCRIPTION: Get a command from the history buffer
169 * PARAMETERS: cmd_num - Index of the desired history entry.
174 * DESCRIPTION: Get a command from the history buffer
183 /* Search history buffer */ in acpi_db_get_history_by_index()
194 /* History buffer is circular */ in acpi_db_get_history_by_index()
202 acpi_os_printf("Invalid history number: %u\n", history_index); in acpi_db_get_history_by_index()
|
| /linux/Documentation/hwmon/ |
| H A D | ltc3815.rst | 44 in1_reset_history Reset input voltage history.
50 in2_reset_history Reset output voltage history.
55 temp1_reset_history Reset temperature history.
60 curr1_reset_history Reset input current history.
66 curr2_reset_history Reset output current history.
|
| H A D | ltc2947.rst | 46 in0_reset_history Write 1 to reset in1 history
56 in1_reset_history Write 1 to reset in2 history
66 curr1_reset_history Write 1 to reset curr1 history
76 power1_reset_history Write 1 to reset power1 history
86 temp1_reset_history Write 1 to reset temp1 history
|
| H A D | ltc4282.rst | 51 in0_reset_history Write 1 to reset in0 history.
64 in1_reset_history Write 1 to reset in1 history.
78 in2_reset_history Write 1 to reset in2 history
88 curr1_reset_history Write 1 to reset curr1 history.
100 power1_reset_history Write 1 to reset power1 history.
|
| H A D | ltc2945.rst | 61 in1_reset_history Write 1 to reset in1 history
70 in2_reset_history Write 1 to reset in2 history
79 curr1_reset_history Write 1 to reset curr1 history
89 power1_reset_history Write 1 to reset power1 history
|
| H A D | ina209.rst | 43 in0_reset_history reset shunt voltage history
56 in1_reset_history reset bus voltage history
68 power1_reset_history reset power history
|
| /linux/net/dccp/ccids/lib/ |
| H A D | packet_history.h | |
| H A D | packet_history.c | |
| H A D | loss_interval.h | |
| /linux/drivers/s390/net/ |
| H A D | fsm.c | 97 printk(KERN_DEBUG "fsm(%s): History:\n", fi->name); in fsm_print_history()
99 int e = fi->history[idx].event; in fsm_print_history()
100 int s = fi->history[idx++].state; in fsm_print_history()
116 fi->history[fi->history_index].state = state; in fsm_record_history()
117 fi->history[fi->history_index++].event = event; in fsm_record_history()
|
| H A D | fsm.h | 26 * Define these to record a history of
53 * Element of State/Event history used for debugging.
74 fsm_history history[FSM_HISTORY_SIZE]; member
|
| /linux/LICENSES/deprecated/ |
| H A D | GFDL-1.2 | 130 "Dedications", "Endorsements", or "History".) To "Preserve the Title"
207 (which should, if there were any, be listed in the History section
226 I. Preserve the section Entitled "History", Preserve its Title, and add
229 there is no section Entitled "History" in the Document, create one
236 it was based on. These may be placed in the "History" section.
299 In the combination, you must combine any sections Entitled "History"
301 "History"; likewise combine any sections Entitled "Acknowledgements",
356 "Dedications", or "History", the requirement (section 4) to Preserve
|
| H A D | GFDL-1.1 | 182 (which should, if there were any, be listed in the History section
200 I. Preserve the section entitled "History", and its title, and add to
203 there is no section entitled "History" in the Document, create one
210 it was based on. These may be placed in the "History" section.
272 In the combination, you must combine any sections entitled "History"
274 "History"; likewise combine any sections entitled "Acknowledgements",
|
| /linux/tools/testing/selftests/powerpc/nx-gzip/ |
| H A D | gunz_test.c | 27 * histlen: history/dictionary length
28 * history: sliding window of up to 32KB of data
406 /* Leave unused space due to history rounding rules */ in decompress_file()
548 * dictionary (history) to NX, which is basically in decompress_file()
556 /* Round up the history size to quadword. Section 2.10 */ in decompress_file()
562 /* Chain in the history buffer to the DDE list */ in decompress_file()
572 /* Up to 32KB history wraps around fifo_out */ in decompress_file()
621 /* Reduce output free space amount not to overwrite the history */ in decompress_file()
648 /* source_sz includes history */ in decompress_file()
755 /* History length error when CE(1)=1 CE(0)=0. */ in decompress_file()
[all …]
|
| /linux/lib/ |
| H A D | dynamic_queue_limits.c | 60 dql->history)) in dql_check_stall()
76 now, dql->history); in dql_check_stall()
205 memset(dql->history, 0, sizeof(dql->history)); in dql_reset()
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | rsb.rst | 206 When a CPU with RRSBA is vulnerable to Branch History Injection
264 .. [#bhi-paper] `Branch History Injection: On the Effectiveness of Hardware Mitigations Against Cro…
266 …History Injection and Intra-mode Branch Target Injection / CVE-2022-0001, CVE-2022-0002 / INTEL-SA…
268 …History Injection and Intra-mode Branch Target Injection / CVE-2022-0001, CVE-2022-0002 / INTEL-SA…
|
| /linux/lib/zlib_dfltcc/ |
| H A D | dfltcc_deflate.c | 135 /* Clear history. */ in dfltcc_deflate()
161 /* Clear history. */ in dfltcc_deflate()
238 /* Honor history and check value */ in dfltcc_deflate()
302 param->hl = 0; /* Clear history */ in dfltcc_deflate()
|
| /linux/drivers/gpu/drm/ |
| H A D | Kconfig | 134 bool "Enable refcount backtrace history in the DP MST helpers"
142 history of each topology reference/dereference will be printed to the
149 bool "Enable backtrace history for lock contention"
157 contention. A history of each drm modeset lock path hitting -EDEADLK
|
| /linux/Documentation/networking/device_drivers/fddi/ |
| H A D | skfp.rst | 25 (8) HISTORY
44 Chapter 6: History of development.
159 6. History
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | verifier_subprog_precision.c | 344 * complicate jump history in parent_callee_saved_reg_precise()
378 * complicate jump history in parent_callee_saved_reg_precise_global()
435 * complicate jump history in parent_callee_saved_reg_precise_with_callback()
482 * complicate jump history in parent_stack_slot_precise()
489 * history in parent_stack_slot_precise()
526 * complicate jump history in parent_stack_slot_precise_global()
533 * history in parent_stack_slot_precise_global()
592 /* ensure we have callback frame in jump history */ in parent_stack_slot_precise_with_callback()
601 * history in parent_stack_slot_precise_with_callback()
713 * history in subprog_spill_into_parent_stack_slot_precise()
[all...] |