Lines Matching refs:that
8 but will help point you in the right direction for that.
28 you plan to do low-level development for that architecture. Though they
36 adheres to the ISO C89 standard, it uses a number of extensions that are
42 and the extensions that it uses, and unfortunately there is no
46 Please remember that you are trying to learn how to work with the
73 The Linux kernel source tree has a large range of documents that are
75 new features are added to the kernel, it is recommended that new
77 When a kernel change causes the interface that the kernel exposes to
78 userspace to change, it is recommended that you send the information or
83 Here is a list of files that are in the kernel source tree that are
92 packages that are necessary to build and run the kernel
148 A list of external documentation that pertains to kernel
156 The kernel also has a large number of documents that can be
177 first, before asking something that has already been answered in the
178 past.) It also has an IRC channel that you can use to ask questions in
179 real-time, and a lot of helpful documentation that is useful for
192 problems that need to be cleaned up and fixed within the Linux kernel
198 If you already have a chunk of code that you want to put into the kernel
208 tools. One such tool that is particularly recommended is the Linux
234 Linus, usually the patches that have already been included in the
240 only patches that do not include new features that could affect the
241 stability of the whole kernel. Please note that a whole new driver
244 is self-contained and does not affect areas outside of the code that
255 that list to zero before declaring the kernel to be "ready," but, in
303 onto such a subsystem kernel tree so that conflicts between the
337 bugs. Users are encouraged to report all bugs that they find in this
377 It is highly recommended that you search the archives about the topic
400 to tune that by adding fancy mail-headers, people will not like it.
410 to comment on individual lines of your patch, which works only that way.
411 Make sure you use a mail program that does not mangle spaces and tab
413 to apply your own patch by yourself. If that doesn't work, get your
445 In a community that is looking for the best technical solution possible,
450 toward a solution that is right.
452 It is normal that the answers to your first patch might simply be a list
453 of a dozen things you should correct. This does _not_ imply that your
463 development environments. Here are a list of things that you can try to
468 - "Here is a patch that explains what I am trying to describe."
470 - "Here is a series of small patches that..."
479 - "Here is my 1000 page design document that describes my idea"
481 - "Here's a 5000 line patch that..."
499 recommended that you check your emails to make sure they make sense in
510 should also be introduced very early in the development process, so that
512 community feel that you are working with them, and not simply using them
515 that almost all of the time.
519 1) Small patches increase the likelihood that your patches will be
551 chunks that they may get already accepted, even when your whole task is
554 Also realize that it is not acceptable to send patches for inclusion
555 that are unfinished and will be "fixed up later."
588 improvement that requires a lot of patience and determination. But