Sanidhya, Sorry I haven't been very responsive, but I'm glad to see your progress here. Once you make the recommended changes, try using 'git format-patch' and 'git send-email' to pick and send the patch to the mailinglists. On Tue, Dec 01, 2015 at 08:42:28AM +0000, Sanidhya Solanki wrote: > Patch moves the headers found in the "skein_block.c" to "skein_block.h". Please reword: The original code defined macros in the source code, making it harder to read. Move them to the header file. > Compiled & checked: no errors found. If you want to let us know this, you can put these kinds of comments below the '---' ... > Signed-off-by: Sanidhya Solanki <jpage@xxxxxxxxxxx> > --- Which is here. That will prevent them from becoming a part of the commit log. > drivers/staging/skein/skein_block.c | 321 > ----------------------------------- > drivers/staging/skein/skein_block.h | 323 > ++++++++++++++++++++++++++++++++++++ > 2 files changed, 323 insertions(+), 321 deletions(-) using the git tools mentioned above will prevent these kinds of wrapping problems, which also affect the content of the patch. Also, if this completes the TODO item, please include the change removing the item from TODO. Since this is your first submission, I'll toss this out there: Don't go redo the work to make the recommended changes. git is designed to help with this. Say you were developing on the git branch 'my_changes', $ git checkout -b my_changes_v2 my_changes $ $EDITOR drivers/staging/skein/TODO $ git add drivers/staging/skein/TODO $ git commit -m "fixup: add TODO changes" $ git rebase -i HEAD^^ change 'pick' to 'fixup' for the last commit save and exit $ git show confirm one commit has everything $ git format-patch ... $ $EDITOR 0001-*.patch $ git send-email ... If it gets all fouled up, don't panic. you can checkout 'my_changes' and it's in it's original state. :-) hth, Jason. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
