[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <998958447.68928.1500213238028@ox.hosteurope.de>
Date: Sun, 16 Jul 2017 15:53:57 +0200 (CEST)
From: Marcus Wolf <marcus.wolf@...f-entwicklungen.de>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: robh+dt@...nel.org, linux-kernel@...r.kernel.org,
devel@...verdev.osuosl.org, grant.likely@...aro.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 1/1] drivers/staging/pi433: New driver
Hi Greg,
like I wrote before - unfortunally I couldn't find a git command, squashing
all my commits into one single patch. Therfore I copy and pasted the patch
manually.
Never the less, the first three rows were copied from a patch, originally
generated by git.
I used
git format-patch master --stdout -p > pi433_patch
for the first rows
and
git diff master > pi433_patch
fot the dif/patch itself.
If someone could help me with better git commands, I would be happy :-)
Thanks a lot,
Marcus
> Greg KH <gregkh@...uxfoundation.org> hat am 16. Juli 2017 um 12:15
> geschrieben:
>
>
> On Sun, Jul 16, 2017 at 11:52:32AM +0200, Wolf Entwicklungen wrote:
> > From: Marcus Wolf <linux@...f-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
>
Powered by blists - more mailing lists