Lines Matching refs:what
49 been created over time based on what they have found to work best for
87 what is necessary to do to configure and build the kernel. People
144 happen, and what to do if you want to get a change into one of these
149 development. Please consult this list if you do not find what you
153 A good introduction describing exactly what a patch is and how to
195 and possibly be pointed in the direction of what to go work on next, if
259 It is worth mentioning what Andrew Morton wrote on the linux-kernel
285 documents what kinds of changes are acceptable for the -stable tree, and
300 development in source repositories. That way, others can see what is
328 This way, the -next kernel gives a summary outlook onto what will be
342 template for how to report a possible kernel bug, and details what kind
384 MAINTAINERS file for a list of what these lists are for the different
424 on its technical merits and those alone. So, what should you be
468 - "Here is a patch that explains what I am trying to describe."
509 the exact opposite of what companies are used to doing. Your proposal
511 you can receive feedback on what you are doing. It also lets the
569 When sending in your patches, pay special attention to what you say in
578 For more details on what this should all look like, please see the