[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1FB5E1D5CA062146B38059374562DF7289F076BD@TK5EX14MBXC128.redmond.corp.microsoft.com>
Date: Mon, 27 Sep 2010 02:52:20 +0000
From: Haiyang Zhang <haiyangz@...rosoft.com>
To: Greg KH <greg@...ah.com>
CC: "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"'devel@...verdev.osuosl.org'" <devel@...verdev.osuosl.org>,
"'virtualization@...ts.osdl.org'" <virtualization@...ts.osdl.org>,
"'gregkh@...e.de'" <gregkh@...e.de>,
Hank Janssen <hjanssen@...rosoft.com>
Subject: RE: [PATCH 1/1] Rename camel case variables in channel.c (updated
again)
> From: Greg KH [mailto:greg@...ah.com]
> This patch is mime-encoded and I'm getting tired of having to convert
> it
> before I can apply it.
>
> Can you please fix up your email client/server to not do this? I
> should
> be able to take the raw email and apply the patch with the 'patch'
> command.
>
> And yes, I know git-am handles mime messages and I use it to apply the
> patch, but I still use 'patch' to verify things are sane before
> commiting the patch for real.
>
> Care to resend?
I checked the email I sent on Friday, it was in "Plain Text" format.
This was the same format I used for my patches which were accepted
previously. Maybe Outlook server converted this one to MIME format?
I'm not sure.
I have attached the patch in Linux text format, which I have verified
with 'patch' command. No error:
linux-next> patch -p1 <0924.2-Rename-camel-case-variables-in-channel.c.patch
patching file drivers/staging/hv/channel.c
linux-next>
Could you try the attached patch on your side?
Thanks,
-Haiyang
Download attachment "0924.2-Rename-camel-case-variables-in-channel.c.patch" of type "application/octet-stream" (45955 bytes)
Powered by blists - more mailing lists