virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Greg KH <greg@kroah.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
	"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
	Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH 1/1] Rename camel case variables in channel.c  (updated again)
Date: Sun, 26 Sep 2010 23:10:29 -0700	[thread overview]
Message-ID: <20100927061029.GC22319@suse.de> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF7289F076BD@TK5EX14MBXC128.redmond.corp.microsoft.com>

On Mon, Sep 27, 2010 at 02:52:20AM +0000, Haiyang Zhang wrote:
> > From: Greg KH [mailto:greg@kroah.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

  reply	other threads:[~2010-09-27  6:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1FB5E1D5CA062146B38059374562DF7289ED89CF@TK5EX14MBXC130.redmond.corp.microsoft.com>
2010-09-23 22:38 ` [PATCH 1/1] Rename camel case variables in channel.c (updated) Joe Perches
2010-09-24 16:08   ` Haiyang Zhang
2010-09-24 16:06 ` [PATCH 1/1] Rename camel case variables in channel.c (updated again) Haiyang Zhang
     [not found] ` <1FB5E1D5CA062146B38059374562DF7289EDBC9E@TK5EX14MBXC130.redmond.corp.microsoft.com>
2010-09-24 17:29   ` Joe Perches
2010-09-27  1:19   ` Greg KH
2010-09-27  2:52     ` Haiyang Zhang
2010-09-27  6:10       ` Greg KH [this message]
2010-09-27 17:57         ` Haiyang Zhang
2010-09-27 19:32           ` Greg KH
2010-09-27 22:59             ` Haiyang Zhang
2010-09-28  1:25               ` Greg KH

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=20100927061029.GC22319@suse.de \
    --to=gregkh@suse.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=haiyangz@microsoft.com \
    --cc=hjanssen@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).