Lines Matching full:but

76 behavior is compliant but the implementation is obfuscatory).
113 - The cost of one administrative interface is incremental, but costs
142 - dprintk can show detailed information, but can be enabled only
146 - Counters are always on, but provide little information about
153 - dynamic tracing, such as kprobes or eBPF, are quite flexible but
237 may suggest stable tagging, but be aware that many version
259 This is not a rejection, but simply a correction of the submission
289 Design documentation is welcome, but as cover letters are not
297 Review comments from maintainers might be politely stated, but in
317 reviewers, but potentially many sources of contributions. The
323 There isn't a formal review process for NFSD, but we like to see
364 nfsd-testing gauntlet, but are then applied to the nfsd-fixes
387 Cc's when you post your patches. This is generally a nuisance, but
415   but I don't know why" is not acceptable.
454 There is no one way to make an official feature request, but
478 design, but are terms of art in the software trade, not used in
509   MAINTAINERS file as a reviewer, but who is an area expert.
544   and strikes during conflicts, but is also responsible for ensuring