stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Greg KH <greg@kroah.com>
Cc: Li Zefan <lizefan@huawei.com>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [kernel.org PATCH] Li Zefan is now the 3.4 stable maintainer
Date: Fri, 5 Sep 2014 15:27:50 -0700	[thread overview]
Message-ID: <20140905222750.GA19219@roeck-us.net> (raw)
In-Reply-To: <20140905214930.GD30221@kroah.com>

On Fri, Sep 05, 2014 at 02:49:30PM -0700, Greg KH wrote:
> > >>
> > >>Problem is that the pending patch got converted to use <cr><lf> instead of
> > >>just <lf> as common in Linux. When I try to apply it with "git quiltimport",
> > >>it bails out with "trailing whitespace" errors. "git am" with the individual
> > >>patch works fine for some reason, though.
> > >>
> > >>I can try to find a workaround, but it would be better to have the file in
> > >>linux file format to start with. Would that be possible ?
> > >>
> > >
> > >Yeah, I've fixed it. I'll run dos2unix for every patch file.
> > >
> > 
> > Yes, it now works. Wonder how it comes that the patch in Greg's patch tree
> > didn't have the problem. Any idea ?
> 
> What patch in my tree has dos line endings?  None should...
> 
The patch in your tree is fine. The same patch in Li's tree
had the problem, though he fixed it now.

Guenter

  reply	other threads:[~2014-09-05 22:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 23:08 [kernel.org PATCH] Li Zefan is now the 3.4 stable maintainer Greg KH
2014-08-26 23:20 ` Konstantin Ryabitsev
2014-08-27  0:12 ` Josh Boyer
2014-08-27  4:59 ` Guenter Roeck
2014-09-04  7:24   ` Li Zefan
2014-09-04 18:39     ` Guenter Roeck
2014-09-05  7:55       ` Li Zefan
2014-09-05 13:58         ` Guenter Roeck
2014-09-05 14:24           ` Shuah Khan
2014-09-05 21:49           ` Greg KH
2014-09-05 22:27             ` Guenter Roeck [this message]
2014-09-10  2:56           ` Li Zefan
2014-08-27  5:13 ` Willy Tarreau

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=20140905222750.GA19219@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).