Hi Greg,

I still need it in a format I can apply it in (i.e. proper subject,
changelog text, signed-off-by, etc.) Can you do that?

 
Yes, I will. But I need to know how. The patch on the first mail, I generated by
git format-patch master --stdout -p > pi433_patch
But that lead to several patches - one for each commit I did on my local git
repo.
Today, I searched on the net, how to squasch it together in one patch and found
git diff master > pi433_patch
 
 
Sorry for annoying you with newbie-problems,
 
Marcus

Greg KH [off-list ref] hat am 15. Juli 2017 um 13:24
geschrieben:


On Sat, Jul 15, 2017 at 01:15:43PM +0200, Marcus Wolf wrote:

quoted

Hi Greg,

thanks for your reply :-)

Today I moved the documentation and header files to drivers/staging/pi433
and
fromated it as a single patch.

Cheers,

Marcus

I still need it in a format I can apply it in (i.e. proper subject,
changelog text, signed-off-by, etc.) Can you do that?

Also, for staging drivers, I need a TODO file, much like the existing
drivers/staging/*/TODO files saying what needs to be done with the code
in order to get it out of staging.

And finally, your patch seemed to have the whitespace corrupted and was
line-wrapped, making it impossible to apply even if I could have :(

thanks,

greg k-h