mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcus Wolf <marcus.wolf@wolf-entwicklungen.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: robh+dt@kernel.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org, grant.likely@linaro.org,
	devicetree@vger.kernel.org
Subject: Re: Submit of a driver for Pi433 - a radio module for Raspberry Pi
Date: Sat, 15 Jul 2017 14:59:25 +0200 (CEST)	[thread overview]
Message-ID: <89433969.66090.1500123565835@ox.hosteurope.de> (raw)
In-Reply-To: <20170715112454.GB1753@kroah.com>

Hi!
 
It's me again. Seems like I also need help on sending the email :-/
 
I checked the whitespace/line wrap problem, but couldn't find any suspicious
lines.
 
What I did:
* Looked into my outbox - the copy of my mail to you seems to be okay...
* I sent the patch once again (just to me) - result: Seems to be fine, too.
 
Maybe you can bounce back my mail? Maybe I'll get an idea what went wrong, if I
see the smashed code...
 
Cheers,
 
Marcus
 

> Greg KH <gregkh@linuxfoundation.org> hat am 15. Juli 2017 um 13:24
> geschrieben:
>
>
> 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
>

  reply	other threads:[~2017-07-15 12:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <281067739.16216.1499788929736@ox.hosteurope.de>
2017-07-12  7:43 ` Greg KH
     [not found]   ` <197075499.65628.1500117344413@ox.hosteurope.de>
2017-07-15 11:24     ` Greg KH
2017-07-15 12:59       ` Marcus Wolf [this message]
2017-07-15 13:02         ` Greg KH
2017-07-15 13:10           ` Marcus Wolf
2017-07-15 13:16             ` Greg KH
     [not found]               ` <1152815224.66246.1500126030682@ox.hosteurope.de>
2017-07-15 13:47                 ` Greg KH
2017-07-15 17:05                   ` Wolf Entwicklungen
2017-07-16  6:45                     ` Greg KH
2017-07-16  9:52                       ` [PATCH 1/1] drivers/staging/pi433: New driver Wolf Entwicklungen
2017-07-16 10:15                         ` Greg KH
2017-07-16 13:53                           ` Marcus Wolf
2017-07-16 14:47                             ` Greg KH
2017-07-17  6:18                         ` kbuild test robot
2017-07-17 13:26                         ` kbuild test robot
2017-07-20 11:23                           ` Marcus Wolf
2017-07-20 11:31                             ` Greg KH
2017-07-20 11:37                             ` Dan Carpenter
2017-07-20 12:27                               ` Geert Uytterhoeven
2017-07-20 15:56                                 ` [PATCH 1/1] staging: pi433: fix problem with division in rf69_set_deviation Marcus Wolf
2017-07-29  0:01                                   ` Greg KH
2017-07-29  8:51                                     ` Marcus Wolf
2017-07-29 22:21                                       ` Greg KH
2017-07-30 15:21                                         ` Marcus Wolf
2017-07-20 15:57                                 ` Test of " Marcus Wolf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89433969.66090.1500123565835@ox.hosteurope.de \
    --to=marcus.wolf@wolf-entwicklungen.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®