From: Greg KH <gregkh@linuxfoundation.org>
To: Wolf Entwicklungen <Marcus.Wolf@Wolf-Entwicklungen.de>
Cc: robh+dt@kernel.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org, grant.likely@linaro.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers/staging/pi433: New driver
Date: Sun, 16 Jul 2017 12:15:31 +0200 [thread overview]
Message-ID: <20170716101531.GA19773@kroah.com> (raw)
In-Reply-To: <39f4e59cae6d241235f8f2cc6eebb33c-EhVcX1pHQwdXWkQFBhENSgEKLlwACzJXX19HAVhEWENbS1kLMF52CEtUX1pBSEwcXlJRL1lQWAheVn4GUFc=-webmailer1@server05.webmailer.hosteurope.de>
On Sun, Jul 16, 2017 at 11:52:32AM +0200, Wolf Entwicklungen wrote:
> From: Marcus Wolf <linux@Wolf-Entwicklungen.de>
> Date: Tue,16 Jul 2017 11:52:06 +0100
> Subject: [PATCH 1/1] drivers/staging/pi433: New driver
Why is this all here in the patch body? Usually git will strip this
out, but in the future, please don't put it here.
I'll try to queue this up in a few days and let's see what breaks :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-16 10:15 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 ` Submit of a driver for Pi433 - a radio module for Raspberry Pi Greg KH
[not found] ` <197075499.65628.1500117344413@ox.hosteurope.de>
2017-07-15 11:24 ` Greg KH
2017-07-15 12:59 ` Marcus Wolf
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 [this message]
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=20170716101531.GA19773@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Marcus.Wolf@Wolf-Entwicklungen.de \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.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