RE: [PATCH 0/3] OMAP4: prcm/clock fixes
> -Original Message- > From: Paul Walmsley [mailto:p...@pwsan.com] > Sent: Thursday, January 21, 2010 2:17 AM > To: Nayak, Rajendra > Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org > Subject: RE: [PATCH 0/3] OMAP4: prcm/clock fixes > > Hi, > > On Tue, 19 Jan 2010, Paul Walmsley wrote: > > > On Tue, 19 Jan 2010, Paul Walmsley wrote: > > > This patch is now posted for any comments or review: > > > > > > > http://www.pwsan.com/omap/patches/omap4_clk_fix/0001-OMAP4-PRC > M-Define-shift-macros-as-n-instead-of-1.patch > > > > Thanks, this is a total "brown paper bag" bug :-( > > > > Queued for 2.6.33-rc. > > Based on some advice from Tony, this patch has been moved to the > for_2.6.34 branch. Please let me know if this causes any problems. Thanks Paul, that should be just fine. > > - Paul > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 0/3] OMAP4: prcm/clock fixes
Hi, On Tue, 19 Jan 2010, Paul Walmsley wrote: > On Tue, 19 Jan 2010, Paul Walmsley wrote: > > This patch is now posted for any comments or review: > > > > http://www.pwsan.com/omap/patches/omap4_clk_fix/0001-OMAP4-PRCM-Define-shift-macros-as-n-instead-of-1.patch > > Thanks, this is a total "brown paper bag" bug :-( > > Queued for 2.6.33-rc. Based on some advice from Tony, this patch has been moved to the for_2.6.34 branch. Please let me know if this causes any problems. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 0/3] OMAP4: prcm/clock fixes
On Tue, 19 Jan 2010, Paul Walmsley wrote: > On Tue, 19 Jan 2010, Nayak, Rajendra wrote: > > > >-Original Message- > > >From: Paul Walmsley [mailto:p...@pwsan.com] > > > > > >Hi Rajendra, > > > > > >On Mon, 18 Jan 2010, Nayak, Rajendra wrote: > > > > > >> Ok, so I will repost it as an attachement since its too big. > > >> Hope that's fine. > > > > > >How about either posting it on a website somewhere and sending > > >a link? Or > > >send it to me and I will post it on the website here. > > > > Ok, I will send you the patch off the list. > > This patch is now posted for any comments or review: > > http://www.pwsan.com/omap/patches/omap4_clk_fix/0001-OMAP4-PRCM-Define-shift-macros-as-n-instead-of-1.patch Thanks, this is a total "brown paper bag" bug :-( Queued for 2.6.33-rc. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 0/3] OMAP4: prcm/clock fixes
On Tue, 19 Jan 2010, Nayak, Rajendra wrote: > >-Original Message- > >From: Paul Walmsley [mailto:p...@pwsan.com] > >Sent: Monday, January 18, 2010 10:42 PM > >To: Nayak, Rajendra > >Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org > >Subject: RE: [PATCH 0/3] OMAP4: prcm/clock fixes > > > >Hi Rajendra, > > > >On Mon, 18 Jan 2010, Nayak, Rajendra wrote: > > > >> Ok, so I will repost it as an attachement since its too big. > >> Hope that's fine. > > > >How about either posting it on a website somewhere and sending > >a link? Or > >send it to me and I will post it on the website here. > > Ok, I will send you the patch off the list. This patch is now posted for any comments or review: http://www.pwsan.com/omap/patches/omap4_clk_fix/0001-OMAP4-PRCM-Define-shift-macros-as-n-instead-of-1.patch - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 0/3] OMAP4: prcm/clock fixes
>-Original Message- >From: Paul Walmsley [mailto:p...@pwsan.com] >Sent: Monday, January 18, 2010 10:42 PM >To: Nayak, Rajendra >Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org >Subject: RE: [PATCH 0/3] OMAP4: prcm/clock fixes > >Hi Rajendra, > >On Mon, 18 Jan 2010, Nayak, Rajendra wrote: > >> Ok, so I will repost it as an attachement since its too big. >> Hope that's fine. > >How about either posting it on a website somewhere and sending >a link? Or >send it to me and I will post it on the website here. Ok, I will send you the patch off the list. Thanks Paul. > >thanks > >- Paul >-- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 0/3] OMAP4: prcm/clock fixes
Hi Rajendra, On Mon, 18 Jan 2010, Nayak, Rajendra wrote: > Ok, so I will repost it as an attachement since its too big. > Hope that's fine. How about either posting it on a website somewhere and sending a link? Or send it to me and I will post it on the website here. thanks - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 0/3] OMAP4: prcm/clock fixes
>-Original Message- >From: Paul Walmsley [mailto:p...@pwsan.com] >Sent: Thursday, January 14, 2010 4:42 AM >To: Nayak, Rajendra >Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org >Subject: Re: [PATCH 0/3] OMAP4: prcm/clock fixes > >Hi Rajendra, > >well, right after I sent this message, I noticed that I was >looking at an >older copy of my lakml inbox. So, > >On Wed, 13 Jan 2010, Paul Walmsley wrote: > >> Patch 1 is missing from both the linux-omap and >linux-arm-kernel mailing >> lists. Too big, perhaps? >> >> Patches 2 and 3 only made it to linux-omap, it seems. At >least, I can't >> find them on linux-arm-kernel. >> >> Anyway, patches 2 and 3 have been queued up for 2.6.33-rc*, >but could you >> please resend the whole series? > >... since patches 2 and 3 have made it to the lists, all you need to >resend is patch 1. Ok, so I will repost it as an attachement since its too big. Hope that's fine. > >thanks, > >- Paul >-- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/3] OMAP4: prcm/clock fixes
Hi Rajendra, well, right after I sent this message, I noticed that I was looking at an older copy of my lakml inbox. So, On Wed, 13 Jan 2010, Paul Walmsley wrote: > Patch 1 is missing from both the linux-omap and linux-arm-kernel mailing > lists. Too big, perhaps? > > Patches 2 and 3 only made it to linux-omap, it seems. At least, I can't > find them on linux-arm-kernel. > > Anyway, patches 2 and 3 have been queued up for 2.6.33-rc*, but could you > please resend the whole series? ... since patches 2 and 3 have made it to the lists, all you need to resend is patch 1. thanks, - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/3] OMAP4: prcm/clock fixes
Hi Rajendra, On Mon, 11 Jan 2010, Nayak, Rajendra wrote: > This series contains prcm register def fixes and clock framework fixes for > omap4. > The patches are generated by updating the scripts which autogenerate the files > modified. > They apply on latest mainline kernel and are intended for the .33-rc series. > > regards, > Rajendra > > Rajendra Nayak (3): > OMAP4: PRCM: Define shift macros as n instead of 1 << n > OMAP4: PRCM: Fix the base address for CHIRONSS reg defines > OMAP4: clocks: Fix the clksel_rate struct DPLL divs Patch 1 is missing from both the linux-omap and linux-arm-kernel mailing lists. Too big, perhaps? Patches 2 and 3 only made it to linux-omap, it seems. At least, I can't find them on linux-arm-kernel. Anyway, patches 2 and 3 have been queued up for 2.6.33-rc*, but could you please resend the whole series? thanks - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
