| /linux-6.15/Documentation/process/ |
| H A D | 3.Early-stage.rst | 82 easy to miss things. Your author has seen the posting of a complete 132 subsystem list, posting there is often preferable to posting on 170 If possible, posting your plans during the early stages can only be 185 If a request-for-comments posting yields little in the way of comments, do 198 public mailing list. The posting of code which has not been cleared for 200 sooner that a company's management and legal staff can agree on the posting
|
| H A D | 5.Posting.rst | 9 of conventions and procedures which are used in the posting of patches; 20 There is a constant temptation to avoid posting patches before they are 24 consider posting in-progress work, or even making a git tree available so 27 When posting code which is not yet considered ready for inclusion, it is a 28 good idea to say so in the posting itself. Also mention any major work 56 As a general rule, putting in some extra thought before posting code almost 63 The preparation of patches for posting can be a surprising amount of work, 134 So now you have a perfect series of patches for posting, but the work is 211 latest public review posting of the patch; often this is automatically done 312 relevant people will see your posting on the mailing lists. In particular,
|
| H A D | maintainer-netdev.rst | 203 either missed the posting or have no strong opinions. If the code is ready, 287 Co-posting changes to user space components 314 Co-posting selftests 363 with better review coverage. Re-posting large series also increases the mailing 427 Make sure you address all the feedback in your new posting. Do not post a new 432 not as a reply to the previous posting. Change log should include a link 433 to the previous posting (see :ref:`Changes requested`). 461 before posting to the mailing list. The patchwork build bot instance 501 are auto-constructed and exposed to intentional malicious patch posting,
|
| H A D | code-of-conduct.rst | 60 address, posting via an official social media account, or acting as an appointed
|
| H A D | 6.Followthrough.rst | 10 posting patches indicates a transition into the next stage of the process, 13 It is a rare patch which is so good at its first posting that there is no
|
| H A D | 1.Intro.rst | 32 :ref:`development_posting` talks about the process of posting patches for 38 :ref:`development_followthrough` covers what happens after posting patches; the
|
| H A D | submitting-patches.rst | 338 Top-posting is strongly discouraged in Linux kernel development 346 Q: Were do I find info about this thing called top-posting? 348 Q: Why is top-posting such a bad thing? 349 A: Top-posting.
|
| H A D | maintainer-kvm-x86.rst | 309 if a bug is really truly the end of the world before posting a fix without a 363 in reply to the original posting (cover letter for multi-patch series). The
|
| H A D | 2.Process.rst | 438 read. (i.e. avoid top-posting -- the practice of putting your answer above
|
| /linux-6.15/Documentation/driver-api/ |
| H A D | io_ordering.rst | 50 pending writes before actually posting the read to the chipset, preventing
|
| /linux-6.15/Documentation/nvdimm/ |
| H A D | maintainer-entry-profile.rst | 33 necessarily before initial posting. Contact the list if you need help
|
| /linux-6.15/Documentation/maintainer/ |
| H A D | maintainer-entry-profile.rst | 63 their first posting for consideration before this point. Patches that
|
| H A D | feature-and-driver-maintainers.rst | 49 legal footers, no top posting, etc.)
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | debugfs-intel-iommu | 51 remapping and Interrupt posting.
|
| /linux-6.15/Documentation/RCU/ |
| H A D | rcubarrier.rst | 150 re-posting themselves. This will not be necessary in most cases, since 173 from posting new timers, cancel (or wait for) all the already-posted
|
| H A D | RTFP.txt | 1247 First posting showing how RCU can be safely adapted for 2264 First posting of expedited RCU to be accepted into -tip. 2278 First posting of simple and fast preemptible RCU.
|
| /linux-6.15/Documentation/admin-guide/blockdev/ |
| H A D | floppy.rst | 243 Be sure to read the FAQ before mailing/posting any bug reports!
|
| /linux-6.15/Documentation/trace/ |
| H A D | hisi-ptt.rst | 102 increase the related buffer watermark to avoid frequently posting and
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/amazon/ |
| H A D | ena.rst | 196 posting according to static interrupt delay value. The interrupt delay
|
| /linux-6.15/Documentation/nvme/ |
| H A D | nvme-pci-endpoint-target.rst | 41 After posting completion entries in a completion queue, the driver uses the
|
| /linux-6.15/Documentation/translations/sp_SP/process/ |
| H A D | submitting-patches.rst | 373 Q: ¿Dónde puedo encontrar información sobre esto que se llama top-posting? 375 Q: ¿Por qué es tan malo el top-posting? 376 A: Top-posting.
|
| H A D | 2.Process.rst | 475 respuesta sea más fácil de leer. (Es decir, evite top-posting – la
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| H A D | counters.rst | 430 - Number of times NAPI is triggered by XSK wakeups by posting a NOP to 729 the device typically ensures not posting the CQE.
|
| /linux-6.15/Documentation/PCI/ |
| H A D | pci.rst | 545 often requires some additional changes. Specifically, "write posting"
|
| /linux-6.15/Documentation/arch/powerpc/ |
| H A D | hvcs.rst | 574 distribution company that provided your OS or by posting issues to the
|