linux-kernel - Re: Submit of a driver for Pi433 - a radio module for Raspberry Pi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170715112454.GB1753@kroah.com>
Date:   Sat, 15 Jul 2017 13:24:54 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Marcus Wolf <marcus.wolf@...f-entwicklungen.de>
Cc:     robh+dt@...nel.org, linux-kernel@...r.kernel.org,
        devel@...verdev.osuosl.org, grant.likely@...aro.org,
        devicetree@...r.kernel.org
Subject: Re: Submit of a driver for Pi433 - a radio module for Raspberry Pi

On Sat, Jul 15, 2017 at 01:15:43PM +0200, Marcus Wolf wrote:
> 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