Lines Matching refs:what

52 been created over time based on what they have found to work best for
93     what is necessary to do to configure and build the kernel.  People
155     happen, and what to do if you want to get a change into one of these
160     development.  Please consult this list if you do not find what you
164     A good introduction describing exactly what a patch is and how to
216 and possibly be pointed in the direction of what to go work on next, if
272 It is worth mentioning what Andrew Morton wrote on the linux-kernel
299 in the kernel tree documents what kinds of changes are acceptable for
307 development in source repositories.  That way, others can see what is
337 This way, the linux-next gives a summary outlook onto what will be
347 what kind of information is needed by the kernel developers to help track
391 MAINTAINERS file for a list of what these lists are for the different
434 on its technical merits and those alone.  So, what should you be
482     - "Here is a patch that explains what I am trying to describe."
524 the exact opposite of what companies are used to doing.  Your proposal
526 you can receive feedback on what you are doing.  It also lets the
585 When sending in your patches, pay special attention to what you say in
595 For more details on what this should all look like, please see the