Upstream patch status?? (v3.6-rc1 out)
Guys, As v3.6-rc1 is now out we really need to get some of these simpler patches upstream and accepted NOW. Please provide status updates if the patch is upstream already let me know. [P1025RDB] (some major differences between upstream and internal P1025RDB support) powerpc/85xx: Add Quicc Engine support for p1025rdb P1025RDB Zhicheng Fan powerpc/dts: Add ucc uart support for p1025rdb P1025RDB Zhicheng Fan powerpc/dts: Add dts for p1025rdb board P1025RDBZhicheng Fan [P1022DS] (this is trivial, please take 10m and get this updated and submitted) powerpc/mpc85xx: p1022ds support the MTD for NOR and NAND flash P1022DS Jerry Huang [DTS] (Stuart, can you help and close) powerpc/e5500: Add power isa properties to comply with ePAPR 1.1EPAPR Liu Yu powerpc/e500mc: Add power isa properties to comply with ePAPR 1.1 EPAPR Liu Yu powerpc/e500v2: Add power isa properties to comply with ePAPR 1.1 EPAPR Liu Yu [MSI] (I think upstream, Timur please verify) powerpc/fsl: add MSI support for the Freescale hypervisor KVM/HV Timur Tabi [CORE] powerpc/booke: Re-organize debug code COREKumar Gala [USB] (Again, this is trivial and spend 10m and send upstream) usb/fsl: fixed USB wakeup USB Zhao Chenhui [LBC] mtd: elbc nand: use drvdata to only remove the relevant chipLBC Scott Wood [SATA] libata-pmp: add schedule timeout to support some PMP cards SATA Jerry Huang fsl-sata: workaround to fix the exception of link layer SATAQiang Liu - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Upstream patch status?? (v3.6-rc1 out)
Sorry, This meant for an internal fsl list. - k On Aug 3, 2012, at 8:51 AM, Gala Kumar-B11780 wrote: Guys, As v3.6-rc1 is now out we really need to get some of these simpler patches upstream and accepted NOW. Please provide status updates if the patch is upstream already let me know. [P1025RDB] (some major differences between upstream and internal P1025RDB support) powerpc/85xx: Add Quicc Engine support for p1025rdb P1025RDB Zhicheng Fan powerpc/dts: Add ucc uart support for p1025rdbP1025RDB Zhicheng Fan powerpc/dts: Add dts for p1025rdb board P1025RDB Zhicheng Fan [P1022DS] (this is trivial, please take 10m and get this updated and submitted) powerpc/mpc85xx: p1022ds support the MTD for NOR and NAND flash P1022DS Jerry Huang [DTS] (Stuart, can you help and close) powerpc/e5500: Add power isa properties to comply with ePAPR 1.1 EPAPR Liu Yu powerpc/e500mc: Add power isa properties to comply with ePAPR 1.1 EPAPR Liu Yu powerpc/e500v2: Add power isa properties to comply with ePAPR 1.1 EPAPR Liu Yu [MSI] (I think upstream, Timur please verify) powerpc/fsl: add MSI support for the Freescale hypervisor KVM/HV Timur Tabi [CORE] powerpc/booke: Re-organize debug code COREKumar Gala [USB] (Again, this is trivial and spend 10m and send upstream) usb/fsl: fixed USB wakeup USB Zhao Chenhui [LBC] mtd: elbc nand: use drvdata to only remove the relevant chip LBC Scott Wood [SATA] libata-pmp: add schedule timeout to support some PMP cardsSATA Jerry Huang fsl-sata: workaround to fix the exception of link layer SATA Qiang Liu - k ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: patch status
A URL to it would be fine. I still haven't managed to find it, but perhaps the 'ALL available documents/types listed' link on this page: http://www.appliedmicro.com/MyAMCC/jsp/public/productDetail/product_de tail.jsp?productID=PPC460SX doesn't really mean all? Looks like need a login to get the actual engineering manual. It is also whipped with CD of evaluation board. Just reply to the patch is fine. No need to send a new one if there are no code changes. There are no new changes. I will reply to the patch. Thanks, Marri ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
patch status
Hi Ben, Did you get the chance to review the patch I sent it on Dec-1 2009 http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-December/078436.html Regards, MArri ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: patch status
On Mon, Dec 07, 2009 at 02:01:58PM -0800, Tirumala Reddy Marri wrote: Hi Ben, Did you get the chance to review the patch I sent it on Dec-1 2009 http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-December/078436.html Ben has to review lots of patches. Please be patient. Also, your patch is tracked via patchwork here: http://patchwork.ozlabs.org/patch/39865/ so you can see the state as it progresses. Further, it would have been helpful to CC the maintainer of the 4xx sub-arch (me) since it impacts that platform and you could have gotten some review more quickly. I didn't notice it until this afternoon. Lastly, your patch has lots of magical values in it. While I have no doubt they are correct, I can't find any documentation for 460SX on the AMCC website aside from some small product briefs. Perhaps I've overlooked the CPU manual, but since I don't have such a board or the manual for it, it would be nice to know what kind of testing has been done with this patch. A simple statement such as tested on kernel version with a network, raid, whatever pci-e card successfully would go a long way. This is not a rant or complaint about the code. Just a reminder that the community doesn't always move at the pace we would all like :). I'll try and look over the patch more carefully tomorrow. josh ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: patch status
Josh, Sorry for my ignorance that I did not copy you first. From now on I will make sure you are cc'ed . I will send you the copy of user manual which is available on external website. Should I send new patch with what is tested with this change or is it enough to write in email ? Regards, Marri -Original Message- From: Josh Boyer [mailto:jwbo...@linux.vnet.ibm.com] Sent: Monday, December 07, 2009 4:53 PM To: Tirumala Reddy Marri Cc: b...@kernel.crashing.org; linuxppc-dev@lists.ozlabs.org Subject: Re: patch status On Mon, Dec 07, 2009 at 02:01:58PM -0800, Tirumala Reddy Marri wrote: Hi Ben, Did you get the chance to review the patch I sent it on Dec-1 2009 http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-December/078436.htm l Ben has to review lots of patches. Please be patient. Also, your patch is tracked via patchwork here: http://patchwork.ozlabs.org/patch/39865/ so you can see the state as it progresses. Further, it would have been helpful to CC the maintainer of the 4xx sub-arch (me) since it impacts that platform and you could have gotten some review more quickly. I didn't notice it until this afternoon. Lastly, your patch has lots of magical values in it. While I have no doubt they are correct, I can't find any documentation for 460SX on the AMCC website aside from some small product briefs. Perhaps I've overlooked the CPU manual, but since I don't have such a board or the manual for it, it would be nice to know what kind of testing has been done with this patch. A simple statement such as tested on kernel version with a network, raid, whatever pci-e card successfully would go a long way. This is not a rant or complaint about the code. Just a reminder that the community doesn't always move at the pace we would all like :). I'll try and look over the patch more carefully tomorrow. josh ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: patch status
On Mon, Dec 07, 2009 at 05:41:35PM -0800, Tirumala Reddy Marri wrote: Josh, Sorry for my ignorance that I did not copy you first. From now on I No reason to apologize. Working with the Linux community is a learning process. will make sure you are cc'ed . I will send you the copy of user manual which is available on external website. A URL to it would be fine. I still haven't managed to find it, but perhaps the 'ALL available documents/types listed' link on this page: http://www.appliedmicro.com/MyAMCC/jsp/public/productDetail/product_detail.jsp?productID=PPC460SX doesn't really mean all? Should I send new patch with what is tested with this change or is it enough to write in email ? Just reply to the patch is fine. No need to send a new one if there are no code changes. josh ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
ft_ordered removal patch status?
Hi Paul, Is there a reason this hasn't been picked up: http://ozlabs.org/pipermail/linuxppc-dev/2007-May/035906.html It fixes a build warning in the tree and removes some dead code. It appears to still apply cleanly to the top of your tree if there are issues please let me know so I can fix them. Thanks, Becky ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
