Commit 3e1ded1fff32d8af8cc5eec22c56797621ea6649
Committed by
Tom Rini
1 parent
3ef46a998a
Exists in
v2017.01-smarct4x
and in
37 other branches
buildman: Fix some typos in README
Signed-off-by: Dirk Behme <dirk.behme@gmail.com> Acked-by: Simon Glass <sjg@chromium.org>
Showing 1 changed file with 7 additions and 7 deletions Side-by-side Diff
tools/buildman/README
... | ... | @@ -42,7 +42,7 @@ |
42 | 42 | Buildman is a builder. It is not make, although it runs make. It does not |
43 | 43 | produce any useful output on the terminal while building, except for |
44 | 44 | progress information (except with -v, see below). All the output (errors, |
45 | -warnings and binaries if you are ask for them) is stored in output | |
45 | +warnings and binaries if you ask for them) is stored in output | |
46 | 46 | directories, which you can look at while the build is progressing, or when |
47 | 47 | it is finished. |
48 | 48 | |
... | ... | @@ -121,7 +121,7 @@ |
121 | 121 | means to build all arm boards except nvidia, freescale and anything ending |
122 | 122 | with 'ball'. |
123 | 123 | |
124 | -It is convenient to use the -n option to see whaat will be built based on | |
124 | +It is convenient to use the -n option to see what will be built based on | |
125 | 125 | the subset given. |
126 | 126 | |
127 | 127 | Buildman does not store intermediate object files. It optionally copies |
... | ... | @@ -371,7 +371,7 @@ |
371 | 371 | |
372 | 372 | |
373 | 373 | To find out how the build went, ask for a summary with -s. You can do this |
374 | -either before the build completes (presumably in another terminal) or or | |
374 | +either before the build completes (presumably in another terminal) or | |
375 | 375 | afterwards. Let's work through an example of how this is used: |
376 | 376 | |
377 | 377 | $ ./tools/buildman/buildman -b lcd9b -s |
... | ... | @@ -439,7 +439,7 @@ |
439 | 439 | |
440 | 440 | At commit 16, the error moves - you can see that the old error at line 120 |
441 | 441 | is fixed, but there is a new one at line 126. This is probably only because |
442 | -we added some code and moved the broken line father down the file. | |
442 | +we added some code and moved the broken line further down the file. | |
443 | 443 | |
444 | 444 | If many boards have the same error, then -e will display the error only |
445 | 445 | once. This makes the output as concise as possible. To see which boards have |
... | ... | @@ -647,8 +647,8 @@ |
647 | 647 | board was built) and by 96 bytes for powerpc. This increase was offset in both |
648 | 648 | cases by reductions in rodata and data/bss. |
649 | 649 | |
650 | -Shown below the summary lines is the sizes for each board. Below each board | |
651 | -is the sizes for each function. This information starts with: | |
650 | +Shown below the summary lines are the sizes for each board. Below each board | |
651 | +are the sizes for each function. This information starts with: | |
652 | 652 | |
653 | 653 | add - number of functions added / removed |
654 | 654 | grow - number of functions which grew / shrunk |
... | ... | @@ -817,7 +817,7 @@ |
817 | 817 | This has mostly be written in my spare time as a response to my difficulties |
818 | 818 | in testing large series of patches. Apart from tidying up there is quite a |
819 | 819 | bit of scope for improvement. Things like better error diffs and easier |
820 | -access to log files. Also it would be nice it buildman could 'hunt' for | |
820 | +access to log files. Also it would be nice if buildman could 'hunt' for | |
821 | 821 | problems, perhaps by building a few boards for each arch, or checking |
822 | 822 | commits for changed files and building only boards which use those files. |
823 | 823 |