On Wed, Jan 6, 2016 at 1:06 AM, Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote:
> It's not really necessary to CC linux-kernel. No one reads it.
> I only send patches there when there isn't another public mailing
> list available.
Actually, cc'ing lkml is still often a good idea, because it's a great
archiving point.
I know lots o people (and I am one) who are *not* on random mailing
lists that discuss particular subsystems, but that get lkml as an
auto-archived thing. Then, when cc'd, you see the back story - in a
way that you do *not* see with the random mailing list that was
specific to a particular subsystem.
There are also tools like patchworks that follow mailing lists - and
yes, it follows many different sublists, but not necessarily all.
Don't get me wrong: lkml is seldom - if ever - the _primary_ list. But
I would violently disagree with some kind of blanket "not really
necessary to CC linux-kernel" statement. It's still very useful
indeed, and it doesn't hurt to cc it for valid patches.
Linus
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
