On Wed, Oct 29, 2014 at 01:49:13PM +0100, Rafał Miłecki wrote: > > Well, I don't think it was public enough then. The 3.16 patches have > > been around for quite some time, some people actually tested it, sent > > some feedbacks, we fixed some issues, before getting it merged. > > > > I don't think this is really the case for 3.18, is it? > > No. Testing & patches are welcome! We've just ported brcm47xx and > bcm53xx patches to be able to actually test it.
Ok. > >> I didn't really spend hours working on 3.18 in some non-public way. I > >> just ported most patches in ~2 hours and pushed what I got. Now I need > >> help on cleaning that up. > >> > >> I'm also not sure about other of your patches. My only guess I ppl > >> didn't focus on them since there wasn't 3.16 in the first place. Or > >> maybe you could send separated patch per patch? > > > > The other patches were not related to 3.16, and were sent as a > > separate patch set. Sending these patches one by one wouldn't make > > much sense. > > Your 4 mvebu patches were sent fine. I was thinking about > v2-0002-mvebu-Add-3.16-kernel-patches-and-configuration.patch > v2-0003-mvebu-Switch-to-3.16.patch > When working on mvebu target and 3.18 support please kindly send them > as e-mail patches. Yeah, I sent them that way because it's actually advertise that way in the documentation, but it felt odd :) Thanks, Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
signature.asc
Description: Digital signature
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
