> Of course, I didn't know there were serious concerns about this
> driver's origin. I hope we aren't confusing this with the atheros
> driver...?
>
> > Please don't let this reverse engineering idiocy hinder wireless driver
> > adoption, we're already falling far behind openbsd who are very successfull
> > reverse engineering lots of wireless chipsets.
>
> This bugbear does seem to keep visiting us. It is a bit of a
> minefield.
>
> I'm inclined to think that Christoph and Arjan are right, that we
> have been too cautious. Of course, neither of these fine gentlemen
> are known for their timidity... :-)
>
> Does not the Signed-off-by: line on a patch submission give us some
> level of "good faith" protection?
I would suggest asking them an explicit "did you copy anything" and make
sure their "we didn't copy" answer is in the description of the original
patch submission.
>
> I'm tempted to take contributors at their word, that they have produced
> their own work and not copied from others. What else do we need?
to a large degree that's all you can do. (of course you can look at the
code for something that looks "obviously not from here" as well, and we
all tend to do that anyway since such stuff tends to highly violate
coding style anyway)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
