Hi Marcel, On Wed, Jul 30, 2014, Marcel Holtmann wrote: > This patch fixes all the block comment issues found by checkpatch.pl and > makes them match the network style now. > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > +/* > + * Based on patches from Jon Smirl <jonsmirl@xxxxxxxxx> > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > +/* > + * Uncompress address function for source and > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > +/* > + * Uncompress address function for source context > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > + /* > + * UDP lenght needs to be infered from the lower layers > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > + /* > + * Traffic Class and FLow Label carried in-line > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > + /* > + * Traffic class carried in-line > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > + /* > + * Flow Label carried in-line > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > + /* > + * replace the compressed UDP head by the uncompressed UDP > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > + /* > + * As we copy some bit-length fields, in the IPHC encoding bytes, > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > + /* > + * Traffic class, flow label > > WARNING: networking block comments don't use an empty /* line, use /* Comment... > + /* > + * Hop limit > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > --- > net/6lowpan/iphc.c | 33 +++++++++++---------------------- > 1 file changed, 11 insertions(+), 22 deletions(-) All 5 patches in this set have been applied to bluetooth-next. Thanks. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
