Li Zefan is now the 3.4 stable maintainer
Greg KH
maintainerPATCH 1/1 Li Zefan is now the 3.4 stable maintainer
Li has agreed to continue to support the 3.4 stable kernel tree until September 2016. Update the releases.html page on kernel.org to reflect this.
content/releases.rst +1 -1
@@ -43,7 +43,7 @@ Longterm 3.14 Greg Kroah-Hartman 2014-03-30 Aug, 2016 3.12 Jiri Slaby 2013-11-03 2016 3.10 Greg Kroah-Hartman 2013-06-30 Sep, 2015 - 3.4 Greg Kroah-Hartman 2012-05-20 Oct, 2014 + 3.4 Li Zefan 2012-05-20 Sep, 2016 3.2 Ben Hutchings 2012-01-04 2016 2.6.32 Willy Tarreau 2009-12-03 Mid-2015 ======== ==================== ============ ==================
Quoted 3 lines · Greg KH
Li has agreed to continue to support the 3.4 stable kernel tree until September 2016. Update the releases.html page on kernel.org to reflect this.
Applied and live, thanks.
Best,
Signature · 3 lines
Konstantin Ryabitsev Linux Foundation Collab Projects Montréal, Québec
Quoted 5 lines · Greg KH
Li has agreed to continue to support the 3.4 stable kernel tree until September 2016. Update the releases.html page on kernel.org to reflect this.
Signed-off-by Greg Kroah-Hartman <[email protected]>
Thanks for sending a reminder to the list for those of us that weren't present at KS.
josh
Quoted 4 lines · Greg KH
Li has agreed to continue to support the 3.4 stable kernel tree until September 2016. Update the releases.html page on kernel.org to reflect this.
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,
Guenter
Quoted 24 lines
Signed-off-by Greg Kroah-Hartman <[email protected]>content/releases.rst +1
-2@@ -43,7 +43,7 @@ Longterm 3.14 Greg Kroah-Hartman 2014-03-30 Aug, 2016 3.12 Jiri Slaby 2013-11-03 2016 3.10 Greg Kroah-Hartman 2013-06-30 Sep, 2015 - 3.4 Greg Kroah-Hartman 2012-05-20 Oct, 2014 + 3.4 Li Zefan 2012-05-20 Sep, 2016 3.2 Ben Hutchings 2012-01-04 2016 2.6.32 Willy Tarreau 2009-12-03 Mid-2015 ======== ==================== ============ ================== --To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi Guenter,
Sorry for my late reply.
Quoted 11 lines · Guenter Roeck
Quoted 4 lines · Greg KH
Li has agreed to continue to support the 3.4 stable kernel tree until September 2016. Update the releases.html page on kernel.org to reflect this.
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.
Quoted 31 lines · Li Zefan
Hi Guenter,
Sorry for my late reply.
Quoted 11 lines · Guenter Roeck
Quoted 4 lines · Greg KH
Li has agreed to continue to support the 3.4 stable kernel tree until September 2016. Update the releases.html page on kernel.org to reflect this.
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.
Quoted 5 lines
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 ?
Alternatively, does anyone know how to apply files in DOS format (lines terminated with cr/lf) using quiltimport ?
Thanks,
Guenter
Quoted 29 lines
Quoted 21 lines
Quoted 6 lines
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.
Quoted 5 lines
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.
Quoted 8 lines
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.
Quoted 34 lines · Li Zefan
Quoted 34 lines
Quoted 21 lines
Quoted 6 lines
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.
Quoted 5 lines
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.
Quoted 6 lines
Quoted 3 lines
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
Quoted 7 lines · Guenter Roeck
Quoted 3 lines
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 ?
I am interested in the answer to your question. I used git am and then ran checkpatch
on the patched file to make sure, there are no warnings. I didn't see any warnings on
the files I patched with git am. Hope that means it is good.
Maybe I should start using dos2unix to be safe.
-- Shuah
Quoted 39 lines · Guenter Roeck
Quoted 38 lines · Li Zefan
Quoted 37 lines
Quoted 21 lines
Quoted 6 lines
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.
Quoted 5 lines
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 ?
Quoted 5 lines
Quoted 2 lines
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...
thanks,
greg k-h
Quoted 10 lines · Greg KH
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
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 ?
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
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
Quoted 39 lines · Guenter Roeck
Quoted 38 lines · Li Zefan
Quoted 37 lines
Quoted 21 lines
Quoted 6 lines
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.
Quoted 5 lines
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 ?
Quoted 6 lines
Quoted 2 lines
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 ?
I saved the patch from my email client, and turned out the lines ended with CRLF.
Quoted 2 lines · Greg KH
Li has agreed to continue to support the 3.4 stable kernel tree until September 2016.
Great! Welcome to Li in this strange world of very long term maintenance :-)
Willy