MMC related patches

MMC related patches

[Madhusudhan]

Hi Tony,

Just a ping on the below patches. I did not see any comments on them. Are
you planning to push them?

Regards,
Madhu

http://marc.info/?l=linux-omap&m=125668573422479&w=2
http://marc.info/?l=linux-omap&m=125624185318767&w=2
http://marc.info/?l=linux-omap&m=125623349405262&w=2
http://marc.info/?l=linux-omap&m=125623339105103&w=2
http://marc.info/?l=linux-omap&m=125623327504912&w=2

Re: MMC related patches

[Tony Lindgren]

* Madhusudhan <madhu.cr@ti.com> [091111 16:02]:
> Hi Tony,
> 
> Just a ping on the below patches. I did not see any comments on them. Are
> you planning to push them?
> 
> Regards,
> Madhu
> 
> http://marc.info/?l=linux-omap&m=125668573422479&w=2
> http://marc.info/?l=linux-omap&m=125624185318767&w=2

OK, adding.

> http://marc.info/?l=linux-omap&m=125623349405262&w=2

This needs to be refreshed against board-zoom-peripherals.c now
in omap for-next. But if it depends on 3630 mux patch,
let's wait on that until we have the new mux framework.

> http://marc.info/?l=linux-omap&m=125623339105103&w=2
> http://marc.info/?l=linux-omap&m=125623327504912&w=2

Adding.

Also, this needs to be refreshed:

http://patchwork.kernel.org/patch/45196/

Thanks for summarizing the patches, that always helps.
Maybe use patchwork.kernel.org links the next time,
as I can directly apply from those?

Or even better, just set a git branch against some static
commit :) (Not against for-next as that's still changing)

BTW, some of these patches I had to unwrap manually again..

Regards,

Tony

RE: MMC related patches

[Madhusudhan]

> -----Original Message-----
> From: Tony Lindgren [mailto:tony@atomide.com]
> Sent: Wednesday, November 11, 2009 8:30 PM
> To: Madhusudhan
> Cc: linux-omap@vger.kernel.org
> Subject: Re: MMC related patches
> 
> * Madhusudhan <madhu.cr@ti.com> [091111 16:02]:
> > Hi Tony,
> >
> > Just a ping on the below patches. I did not see any comments on them.
> Are
> > you planning to push them?
> >
> > Regards,
> > Madhu
> >
> > http://marc.info/?l=linux-omap&m=125668573422479&w=2
> > http://marc.info/?l=linux-omap&m=125624185318767&w=2
> 
> OK, adding.
> 
> > http://marc.info/?l=linux-omap&m=125623349405262&w=2
> 
> This needs to be refreshed against board-zoom-peripherals.c now
> in omap for-next. But if it depends on 3630 mux patch,
> let's wait on that until we have the new mux framework.
> 
Sure, I will rebase and send a new patch. It should not have any dependency
on 3630 mux patch.

> > http://marc.info/?l=linux-omap&m=125623339105103&w=2
> > http://marc.info/?l=linux-omap&m=125623327504912&w=2
> 
> Adding.
> 
> Also, this needs to be refreshed:
> 
> http://patchwork.kernel.org/patch/45196/
> 
This one is an omap4 mmc patch which is already in the tree. Why does this
need to be refreshed?

Regards,
Madhu
 
> Thanks for summarizing the patches, that always helps.
> Maybe use patchwork.kernel.org links the next time,
> as I can directly apply from those?
> 
> Or even better, just set a git branch against some static
> commit :) (Not against for-next as that's still changing)
> 
> BTW, some of these patches I had to unwrap manually again..
> 
> Regards,
> 
> Tony

Re: MMC related patches

[Tony Lindgren]

* Madhusudhan <madhu.cr@ti.com> [091112 14:21]:
> 
> 
> > -----Original Message-----
> > From: Tony Lindgren [mailto:tony@atomide.com]
> > Sent: Wednesday, November 11, 2009 8:30 PM
> > To: Madhusudhan
> > Cc: linux-omap@vger.kernel.org
> > Subject: Re: MMC related patches
> > 
> > * Madhusudhan <madhu.cr@ti.com> [091111 16:02]:
> > > Hi Tony,
> > >
> > > Just a ping on the below patches. I did not see any comments on them.
> > Are
> > > you planning to push them?
> > >
> > > Regards,
> > > Madhu
> > >
> > > http://marc.info/?l=linux-omap&m=125668573422479&w=2
> > > http://marc.info/?l=linux-omap&m=125624185318767&w=2
> > 
> > OK, adding.
> > 
> > > http://marc.info/?l=linux-omap&m=125623349405262&w=2
> > 
> > This needs to be refreshed against board-zoom-peripherals.c now
> > in omap for-next. But if it depends on 3630 mux patch,
> > let's wait on that until we have the new mux framework.
> > 
> Sure, I will rebase and send a new patch. It should not have any dependency
> on 3630 mux patch.

OK, thanks.
 
> > > http://marc.info/?l=linux-omap&m=125623339105103&w=2
> > > http://marc.info/?l=linux-omap&m=125623327504912&w=2
> > 
> > Adding.
> > 
> > Also, this needs to be refreshed:
> > 
> > http://patchwork.kernel.org/patch/45196/
> > 
> This one is an omap4 mmc patch which is already in the tree. Why does this
> need to be refreshed?

Oops, never mind, I'm out of date again :)

Tony