Lines Matching refs:that

11    Note that some subsystems (e.g. wireless drivers) which have a high volume
20    Aside from subsystems like that mentioned above, all network-related Linux
49    Relating that to netdev:  At the beginning of the 2-week merge window,
57    sent to netdev, but knowing the above, you can predict that in advance.
70    is fed back to Linus at regular (~weekly) intervals.  Meaning that the
88    Then once decided, assuming that you use git, use the prefix flag, i.e.
121    There is a patchworks queue that you can see here:
145    Before you jump to go do the above, do note that the normal stable rules
148    impacted.  In addition, you need to convince yourself that you _really_
152    the better the odds that it is an OK candidate for stable.  So scrambling
160    stable, then ensure you write a decent commit log that describes who
162    bug was introduced.  If you do that properly, then the commit will
167    stable that does _not_ belong in the commit log, then use the three
169    temporarily embed that information into the patch that you send.
171 Q: Someone said that the comment style and coding convention is different
181    it is requested that you make it look like this:
187 Q: I am working in existing code that has the former comment style and not the
190 A: Make it the latter style, so that eventually all code in the domain of
193 Q: I found a bug that might have possible security implications or similar.
196 A: No. The current netdev maintainer has consistently requested that people
198    that, then perhaps consider mailing "security@kernel.org" or reading about
204 A: If your changes are against net-next, the expectation is that you
219    is common, don't mis-indent function arguments that span multiple lines.