linux-kernel - Re: [PATCH 1/1] Rename camel case variables in channel.c (updated again)

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 for Android: free password hash cracker in your pocket

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

Date:	Sun, 26 Sep 2010 23:10:29 -0700
From:	Greg KH <gregkh@...e.de>
To:	Haiyang Zhang <haiyangz@...rosoft.com>
Cc:	Greg KH <greg@...ah.com>,
	"'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>,
	Hank Janssen <hjanssen@...rosoft.com>
Subject: Re: [PATCH 1/1] Rename camel case variables in channel.c  (updated
	again)

On Mon, Sep 27, 2010 at 02:52:20AM +0000, Haiyang Zhang wrote:
> > 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?

Yes, that worked, but you do realize you attached it in base64 mode,
right?  That sure isn't going to work...

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/