Lines Matching +full:multi +full:- +full:subsystems
1 .. SPDX-License-Identifier: GPL-2.0
3 .. _netdev-FAQ:
10 -----
12 - designate your patch to a tree - ``[PATCH net]`` or ``[PATCH net-next]``
13 - for fixes the ``Fixes:`` tag is required, regardless of the tree
14 - don't post large series (> 15 patches), break them up
15 - don't repost your patches within one 24h period
16 - reverse xmas tree
19 ------
21 netdev is a mailing list for all network-related Linux stuff. This
25 Note that some subsystems (e.g. wireless drivers) which have a high
32 Aside from subsystems like those mentioned above, all network-related
37 -----------------
43 merge window is closed, and it is called/tagged ``-rc1``. No new
44 features get mainlined after this -- only fixes to the rc1 content are
48 state of churn), and a week after the last vX.Y-rcN was done, the
51 To find out where we are now in the cycle - load the mainline (Linus)
59 (without an ``-rcN`` suffix) - we are most likely in a merge window
60 and ``net-next`` is closed.
63 ------------------------
67 ``net`` tree, and the ``net-next`` tree. As you can probably guess from
69 mainline tree from Linus, and ``net-next`` is where the new code goes
72 - https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
73 - https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
75 Relating that to kernel development: At the beginning of the 2-week
76 merge window, the ``net-next`` tree will be closed - no new changes/features.
78 mainline/Linus via a pull request for vX.Y -- at the same time, the
82 An announcement indicating when ``net-next`` has been closed is usually
86 Do not send new ``net-next`` content to netdev during the
87 period during which ``net-next`` tree is closed.
90 (use ``--subject-prefix='RFC net-next'`` with ``git format-patch``).
92 Shortly after the two weeks have passed (and vX.Y-rc1 is released), the
93 tree for ``net-next`` reopens to collect content for the next (vX.Y+1)
97 ``net-next`` has re-opened yet, simply check the ``net-next`` git
98 repository link above for any new networking-related commits. You may
101 https://netdev.bots.linux.dev/net-next.html
110 -------------------
130 the exact co-maintainer handling patchwork at the time)
132 usually set automatically by the pw-bot
140 sub-maintainer, who will send it on to the networking trees;
142 will usually remain in this state, whether the sub-maintainer
147 pw-bot
149 pw-bot can automatically set patches to this state based
153 Patches are indexed by the ``Message-ID`` header of the emails
155 the value of ``Message-ID`` to the URL above.
170 pw-bot: changes-requested
188 https://netdev.bots.linux.dev/pw-bot.html
209 [PATCH net-next v3] net: make cows go moo
216 Signed-of-by: Joe Defarmer <joe@barn.org>
217 ---
219 - add a note about time-of-day mooing fluctuation to the commit message
221 - fix missing argument in kernel doc for netif_is_bovine()
222 - fix memory leak in netdev_register_cow()
259 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`,
270 reading about http://oss-security.openwall.org/wiki/mailing-lists/distros
274 Co-posting changes to user space components
291 [PATCH net-next 0/3] net: some feature cover letter
292 └─ [PATCH net-next 1/3] net: some feature prep
293 └─ [PATCH net-next 2/3] net: some feature do it
294 └─ [PATCH net-next 3/3] selftest: net: some feature
296 [PATCH iproute2-next] ip: add support for some feature
302 -----------------
304 Attention to detail is important. Re-read your own work as if you were the
306 the ``--strict`` flag. But do not be mindlessly robotic in doing so.
308 end-user visible symptom, the underlying reason as to why it happens,
311 mis-indent function arguments that span multiple lines. If it is your
316 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
326 git format-patch --subject-prefix='PATCH net-next' start..finish
328 Use ``net`` instead of ``net-next`` (always lower case) in the above for
329 bug-fix ``net`` content.
342 with better review coverage. Re-posting large series also increases the mailing
345 Multi-line comments
399 -------
407 Ideally you will have done run-time testing specific to your change,
412 tree (``net`` or ``net-next``) and not e.g. a stable tree or ``linux-next``.
420 https://github.com/kuba-moo/nipa/tree/master/tests
433 Mock-ups and tests based on ``netdevsim`` are strongly encouraged when
445 -----------------------