Lines Matching full:should

46   They should help prioritize development and review work for each release
60   Reviewers should identify themselves with an ``R:`` entry in the kernel
68   The testing lead should identify themselves with an ``M:`` entry in
72   enough detail to identify the person to whom the report should be
75   The bug triagers should identify themselves with a ``B:`` entry in
86   The release manager should identify themselves with an ``M:`` entry in
99   The maintainer for a given LTS release should identify themselves with an
101   Unmaintained LTS kernels should be marked with status ``S: Orphan`` in that
108 - Patches affecting only the filesystem itself should be based against
116 - Any patchset changing XFS should be cc'd in its entirety to linux-xfs.
121   userspace utilities should send the userspace changes as separate
126   When possible, a new regression test case should be written for
141   * **How** will this new feature work?  This should touch on major data
152   The design document should be committed in the kernel documentation
157 - Patchsets for the new tests should be submitted as separate patchsets
164 - Patchsets implementing bug fixes and further code cleanups should put
172 Code submissions targeting the next merge window should be sent between
178 next merge window should be sent between -rc1 and -rc4.