Home
last modified time | relevance | path

Searched refs:PATCH (Results 1 – 21 of 21) sorted by relevance

/Linux-v5.15/Documentation/ABI/stable/
Dprocfs-audit_loginuid3 KernelVersion: 2.6.11-rc2 1e2d1492e178 ("[PATCH] audit: handle loginuid through proc")
19 KernelVersion: 2.6.25-rc7 1e0bd7550ea9 ("[PATCH] export sessionid alongside the loginuid in procfs")
/Linux-v5.15/Documentation/translations/ja_JP/
DSubmittingPatches291 11) サブジェクトに「 PATCH 」
294 「 [PATCH] 」を付けることが慣習となっています。これによって Linus や他の
471 Subject: [PATCH 001/123] subsystem: summary phrase
519 「summary phrase」は「Subject: [PATCH tag] <summary phrase>」のように、
/Linux-v5.15/Documentation/translations/zh_CN/process/
Dsubmitting-patches.rst333 10）主题中包含 PATCH
336 由于到linus和linux内核的电子邮件流量很高，通常会在主题行前面加上[PATCH]
521 Subject: [PATCH 001/123] 子系统:一句话概述
557 概述的前缀可以用方括号括起来：“Subject: [PATCH <tag>...] <概述>”。标记
D5.Posting.rst235 [PATCH nn/mm] subsys: one-line description of the patch
/Linux-v5.15/Documentation/translations/zh_TW/process/
Dsubmitting-patches.rst336 10）主題中包含 PATCH
339 由於到linus和linux內核的電子郵件流量很高，通常會在主題行前面加上[PATCH]
524 Subject: [PATCH 001/123] 子系統:一句話概述
560 概述的前綴可以用方括號括起來：「Subject: [PATCH <tag>...] <概述>」。標記
D5.Posting.rst238 [PATCH nn/mm] subsys: one-line description of the patch
/Linux-v5.15/Documentation/networking/
Dnetdev-FAQ.rst101 git format-patch --subject-prefix='PATCH net-next' start..finish
205 [PATCH net-next 0/3] net: some feature cover letter
206 └─ [PATCH net-next 1/3] net: some feature prep
207 └─ [PATCH net-next 2/3] net: some feature do it
208 └─ [PATCH net-next 3/3] selftest: net: some feature
210 [PATCH iproute2-next] ip: add support for some feature
Dmsg_zerocopy.rst52 [PATCH net-next v4 0/9] socket sendmsg MSG_ZEROCOPY
/Linux-v5.15/Documentation/RCU/
DRTFP.txt761 ,Title="Re: {[PATCH]} Initial support for struct {vfs\_cred}"
825 ,Title="[PATCH]updated ipc lock patch"
838 ,Title="Re: {[PATCH]} small fixes in brlock.h"
994 ,Title="{[PATCH]} {RCU} for low latency (experimental)"
1005 ,Title="Re: {[PATCH]} {RCU} for low latency (experimental)"
1029 ,Title="Re: [Lse-tech] [RFC, PATCH] 1/5 rcu lock update:
1118 ,Title="{[RFC\&PATCH] Alternative {RCU} implementation}"
1185 ,Title="{[PATCH 1/3] RCU: \url{rcu_assign_pointer()} removal of memory barriers}"
1198 ,Title="{[PATCH 2/3] SELinux} scalability - convert {AVC} to {RCU}"
1383 ,Title="{[RFC,PATCH] RCU} and {CONFIG\_PREEMPT\_RT} sane patch"
[all …]
/Linux-v5.15/Documentation/translations/zh_CN/doc-guide/
Dcontributing.rst70 [PATCH] PM / devfreq: Fix two malformed kerneldoc comments
/Linux-v5.15/Documentation/process/
Dsubmitting-patches.rst346 [PATCH Vx RESEND] sub/sys: Condensed patch summary
354 Include PATCH in the subject
358 convention to prefix your subject line with [PATCH]. This lets Linus
580 Subject: [PATCH 001/123] subsystem: summary phrase
632 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
646 Subject: [PATCH 2/5] ext2: improve scalability of bitmap searching
647 Subject: [PATCH v2 01/27] x86: fix eflags tracking
648 Subject: [PATCH v2] sub/sys: Condensed patch summary
649 Subject: [PATCH v2 M/N] sub/sys: Condensed patch summary
D5.Posting.rst314 [PATCH nn/mm] subsys: one-line description of the patch
/Linux-v5.15/Documentation/translations/it_IT/process/
Dsubmitting-patches.rst371 [PATCH Vx RESEND] sub/sys: Condensed patch summary
378 Aggiungete PATCH nell'oggetto
382 prefiggere il vostro oggetto con [PATCH]. Questo permette a Linus e agli
607 Subject: [PATCH 001/123] subsystem: summary phrase
658 le parentesi quadre "Subject: [PATCH <tag>...] <summary phrase>".
673 Subject: [PATCH 2/5] ext2: improve scalability of bitmap searching
674 Subject: [PATCH v2 01/27] x86: fix eflags tracking
675 Subject: [PATCH v2] sub/sys: Condensed patch summary
676 Subject: [PATCH v2 M/N] sub/sys: Condensed patch summary
D5.Posting.rst333 [PATCH nn/mm] subsys: one-line description of the patch
/Linux-v5.15/Documentation/bpf/
Dbpf_devel_QA.rst131 git format-patch --subject-prefix='PATCH bpf' start..finish
136 git format-patch --subject-prefix='PATCH bpf-next' start..finish
152 git format-patch --subject-prefix='PATCH bpf-next v2' start..finish
288 The patches need to have a subject prefix of '``[PATCH iproute2
289 master]``' or '``[PATCH iproute2 net-next]``'. '``master``' or
/Linux-v5.15/drivers/media/dvb-frontends/drx39xyj/
Ddrx_driver.h436 #define DRX_VERSIONSTRING(MAJOR, MINOR, PATCH) \ argument
439 DRX_VERSIONSTRING_HELP(PATCH)
/Linux-v5.15/arch/arm/boot/dts/
Dam335x-bone-common.dtsi285 * [PATCH] ARM: dts: am335x-bone* enable pmic-shutdown-controller
/Linux-v5.15/Documentation/admin-guide/media/
Dbuilding.rst330 add ``[PATCH media-build]`` at the e-mail's subject if you submit a new
/Linux-v5.15/Documentation/doc-guide/
Dcontributing.rst85 [PATCH] PM / devfreq: Fix two malformed kerneldoc comments
/Linux-v5.15/Documentation/gpu/
Dtodo.rst669 - [RFC PATCH v2 00/13] Kernel based bootsplash
/Linux-v5.15/Documentation/scsi/
DChangeLog.lpfc915 "[PATCH] use scsi host private data in ->proc_info.