On Tue, 20 Mar 2012, Jason Cooper wrote: > On Tue, Mar 20, 2012 at 02:03:23PM -0400, Nicolas Pitre wrote: > > On Tue, 20 Mar 2012, Jason Cooper wrote: > > > > > I figure most folks will build orion-ehci as a module and use an initrd. > > > > Possibly, however that doesn't mean this shouldn't be fixed anyway. > > Yes, I didn't mean to imply otherwise. I know new patches for v3.4 are > no longer being accepted (they should already be in for-next, right?) > So, I'm not sure what the disposition of this patch should be.
Just send it to arm-soc as usual, identifying it as a fix. Or, given that this is USB related, you might send it to [email protected]. > If it's appropriate to push it into v3.4[-rc?], great. I just didn't > want to assume that and appear to be pushing patches after the for-next > window closed. I'll send it whereever you guys advise. It is always appropriate to send bug fixes. This is the kind of patches for which there is a -rc period. It is too late for v3.3 now as it was released 2 days ago. However if v3.3 is also broken then the fix for v3.4-rc can carry the "CC: [email protected]" annotation so it'll be picked up for v3.3.1 as well. Nicolas _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
