Lines Matching +full:local +full:- +full:timers
1 .. SPDX-License-Identifier: GPL-2.0
7 ---------------------
11 aggregation tree for several sub-maintainer trees. The tip tree gitweb URL
16 - **x86 architecture**
22 x86-specific KVM and XEN patches.
30 mail alias which distributes mails to the x86 top-level maintainer
32 ``linux-kernel@vger.kernel.org``, otherwise your mail ends up only in
35 - **Scheduler**
37 Scheduler development takes place in the -tip tree, in the
38 sched/core branch - with occasional sub-topic trees for
39 work-in-progress patch-sets.
41 - **Locking and atomics**
44 primitives that are connected to locking) takes place in the -tip
45 tree, in the locking/core branch - with occasional sub-topic trees
46 for work-in-progress patch-sets.
48 - **Generic interrupt subsystem and interrupt chip drivers**:
50 - interrupt core development happens in the irq/core branch
52 - interrupt chip driver development also happens in the irq/core
56 - **Time, timers, timekeeping, NOHZ and related chip drivers**:
58 - timekeeping, clocksource core, NTP and alarmtimer development
59 happens in the timers/core branch, but patches are usually applied in
60 a separate maintainer tree and then aggregated into timers/core
62 - clocksource/event driver development happens in the timers/core
64 and then aggregated into timers/core
66 - **Performance counters core, architecture support and tooling**:
68 - perf core and architecture support development happens in the
71 - perf tooling development happens in the perf tools maintainer
74 - **CPU hotplug core**
76 - **RAS core**
78 Mostly x86-specific RAS patches are collected in the tip ras/core
81 - **EFI core**
86 - **RCU**
88 RCU development happens in the linux-rcu tree. The resulting changes
91 - **Various core code components**:
93 - debugobjects
95 - objtool
97 - random bits and pieces
101 ----------------------
158 worker on same CPU and scans the domain->cpu_mask to get the domain
176 time: POSIX CPU timers: Ensure that variable is initialized
178 If cpu_timer_sample_group returns -EINVAL, it will not have written into
183 short-circuiting of && to sample the timer only if the result will
188 posix-cpu-timers: Make set_process_cpu_timer() more robust
219 spin_lock(desc->lock)
221 spin_unlock(desc->lock)
222 spin_lock(desc->lock)
226 spin_unlock(desc->lock) access released resources.
234 rtmutex_lock(&rcu->rt_mutex)
235 spin_lock(&rcu->rt_mutex.wait_lock)
237 spin_lock(&timer->it_lock)
238 spin_lock(&rcu->mutex.wait_lock)
239 --> Interrupt
240 spin_lock(&timer->it_lock)
273 - Fixes: 12char-SHA1 ("sub/sys: Original subject line")
291 Signed-off-by: J.Dev <j.dev@mail>
299 Signed-off-by: J.Dev <j.dev@mail>
305 - Reported-by: ``Reporter <reporter@mail>``
307 - Closes: ``URL or Message-ID of the bug report this is fixing``
309 - Originally-by: ``Original author <original-author@mail>``
311 - Suggested-by: ``Suggester <suggester@mail>``
313 - Co-developed-by: ``Co-author <co-author@mail>``
315 Signed-off-by: ``Co-author <co-author@mail>``
317 Note, that Co-developed-by and Signed-off-by of the co-author(s) must
320 - Signed-off-by: ``Author <author@mail>``
322 The first Signed-off-by (SOB) after the last Co-developed-by/SOB pair is the
325 - Signed-off-by: ``Patch handler <handler@mail>``
331 author. Acks should be given as Acked-by lines and review approvals
332 as Reviewed-by lines.
342 First-tag: .....
361 - Tested-by: ``Tester <tester@mail>``
363 - Reviewed-by: ``Reviewer <reviewer@mail>``
365 - Acked-by: ``Acker <acker@mail>``
367 - Cc: ``cc-ed-person <person@mail>``
373 - Link: ``https://link/to/information``
378 Link: https://lore.kernel.org/email-message-id@here
383 message is to use markdown-like bracketed notation, for example::
389 Link: https://lore.kernel.org/some-msgid@here # [1]
399 Link: https://patch.msgid.link/patch-source-message-id@here
401 Please do not use combined tags, e.g. ``Reported-and-tested-by``, as
410 because companies restructure their websites frequently. Non-'volatile'
429 window closes and a new -rc1 kernel has been released.
471 Some of these options are x86-specific and can be left out when testing
474 .. _maintainer-tip-coding-style:
477 ------------------
488 Multi-line comments::
492 * multi-line comment.
494 * Larger multi-line comments should be split into paragraphs.
552 if (refcount_dec_and_test(&p->refcnt)) {
560 Instead, comments should explain the non-obvious details and document
563 if (refcount_dec_and_test(&p->refcnt)) {
579 To document functions and their arguments please use kernel-doc format
583 * magic_function - Do lots of magic stuff
595 functions in public header files. It might be overkill to use kernel-doc
606 /* Caller must hold foo->lock */
616 lockdep_assert_held(&foo->lock);
706 truncation, expansion and 32/64-bit confusion.
708 u64 is also recommended in code which would become ambiguous for 32-bit
748 Instead, please consider using the kernel-doc format in a comment preceding
755 * struct bar_order - Description of a bar order
819 into globally visible driver templates - it's useful for those symbols
822 Namespace prefixes may be omitted for local static functions and
823 variables. Truly local functions, only called by other local functions,
824 can have shorter descriptive names - our primary concern is greppability
828 helpful for static functions in vendor-specific files. After all, it
829 is already clear that the code is vendor-specific. In addition, vendor
830 names should only be for truly vendor-specific functionality.
836 --------------------
840 (``linux-tip-commits@vger.kernel.org``) and Cc's all people who are
842 Link tag at the end of the tag list to set the In-Reply-To email header so