gregkh / bti

bash twitter ididocy

This URL has Read+Write access

gregkh (author)
Thu Aug 13 11:07:24 -0700 2009
commit  363f9d65dc79816ecee21ee5d0bad3c403680602
tree    c32460336afcc3318622bab86d4355339c8fa3fb
parent  3132627d3a3c045b9a94534afd024777a0f79919
bti / HACKING
100644 27 lines (20 sloc) 1.063 kb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Patches are gladly accepted for bti code, please send them to
greg@kroah.com, or you can use github to send a pull request.
 
The code tree for smubatch is located at:
http://github.com/gregkh/bti
and can be cloned using git from:
git://github.com/gregkh/bti.git
 
If you have never used git before, there are some useful tutorials on
the github.com web site to help you through the learning process.
 
I am trying to follow the Linux kernel coding style with the code
whereever possible. This style is documented in the Linux kernel source
tree in the file Documentation/CodingStyle. Included in the bti code
tree is a script called checkpatch.pl that can automatically check if
your changes are compliant with the guidelines.
 
To test this, using git, generate a patch:
git diff > my_patch
Then run checkpatch.pl against this patch:
./scripts/checkpatch.pl --no-tree my_patch
 
 
Please run your modifications through valgrind if possible. It is safe
to ignore the valgrind errors in the curl and ssl libraries, we can't do
anything about those at this time.