linux-kernel - Re: [kernel.org PATCH] Li Zefan is now the 3.4 stable maintainer

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <5409C19C.4030901@roeck-us.net>
Date:	Fri, 05 Sep 2014 06:58:52 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Li Zefan <lizefan@...wei.com>
CC:	stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [kernel.org PATCH] Li Zefan is now the 3.4 stable maintainer

On 09/05/2014 12:55 AM, Li Zefan wrote:
>>>> Li,
>>>>
>>>> it would be great if you can send me information about your -stable queue,
>>>> ie how you maintain it and where it is located. This will enable me to
>>>> continue testing the stable queue for the 3.4 kernel.
>>>>
>>>
>>> Thanks for testing LTS kernels!
>>>
>>> This is my 3.4.y git tree:
>>>
>>> https://git.kernel.org/cgit/linux/kernel/git/lizf/linux-3.4.y.git/
>>>
>>> And this is the patch queue:
>>>
>>> https://git.kernel.org/cgit/linux/kernel/git/lizf/linux-3.4.y-queue.git/
>>>
>>> I use quilt. When I've added some patches to 3.4.y, I'll update this
>>> queue. The patches and series file are under /patches. Currently there's
>>> already a patch in the queue.
>>>
>>> When I release a new version, I'll clean up the queue by removing all
>>> the files under /patches.
>>>
>>> Hope this is all the information you need. Please tell me if you need
>>> me to slightly adjust my workflow so it's easier for you.
>>
>> It almost works.
>>
>> 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 ?

Guenter

--
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/