Mainlining MTD drivers (lpc32xx)

DISCUSSION Roland Stigge 3 participants 4 messages Aug 6, 2012 – Aug 15, 2012 Memory technology devices (MTD)

Share & tools

Roland Stigge

author

2012-08-06 08:19 UTC #0 lore raw

Hi,

during the v3.5-rc phases, I prepared some drivers (lpc32xx_slc and lpc32xx_mlc) which ended up being accepted into l2-mtd and linux-next. Now I realize that they are not in v3.6-rc1.

Is there anything I can do at this point? Did anything go wrong or is there a reason for postponing?

My apoplogies if I missed sth. - the mailing list archives are currently not accessible from here. Please just point me to relevant information.

Thanks in advance,

Roland

David Woodhouse

2012-08-06 09:13 UTC #1 lore raw

Quoted 8 lines · Roland Stigge

during the v3.5-rc phases, I prepared some drivers (lpc32xx_slc and lpc32xx_mlc) which ended up being accepted into l2-mtd and linux-next. Now I realize that they are not in v3.6-rc1.
Is there anything I can do at this point? Did anything go wrong or is there a reason for postponing?

No, sorry. This is entirely my fault. I failed to get the pull request in to Linus in time for 3.6-rc1. Apologies for that.

Signature · 1 line

dwmw2

Roland Stigge

author

2012-08-06 11:21 UTC #2 lore raw

Quoted 9 lines · David Woodhouse

Quoted 6 lines
during the v3.5-rc phases, I prepared some drivers (lpc32xx_slc and lpc32xx_mlc) which ended up being accepted into l2-mtd and linux-next. Now I realize that they are not in v3.6-rc1.
Is there anything I can do at this point? Did anything go wrong or is there a reason for postponing?
No, sorry. This is entirely my fault. I failed to get the pull request in to Linus in time for 3.6-rc1. Apologies for that.

Any chance for getting it into a 3.6-rc or needing to wait for 3.7?

Will be fine with any decision, just want to prevent misunderstanding...

Thanks,

Roland

Artem Bityutskiy

2012-08-15 10:34 UTC #3 lore raw

Quoted 5 lines · Roland Stigge

Quoted 4 lines · David Woodhouse
Quoted 4 lines
during the v3.5-rc phases, I prepared some drivers (lpc32xx_slc and lpc32xx_mlc) which ended up being accepted into l2-mtd and linux-next. Now I realize that they are not in v3.6-rc1.

Quoted 7 lines

Quoted 5 lines
Quoted 2 lines
Is there anything I can do at this point? Did anything go wrong or is there a reason for postponing?
No, sorry. This is entirely my fault. I failed to get the pull request in to Linus in time for 3.6-rc1. Apologies for that.
Any chance for getting it into a 3.6-rc or needing to wait for 3.7?

I am nod David, but I think no, Linus is not accepting new drivers that late.

Signature · 2 lines

Best Regards,
Artem Bityutskiy