linux-kernel - Re: [PATCH] staging/ion: Add support to get ion handle from dma buf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFzOt0z+NyHhVsD2wsr6sfA4Un1RDb46tACiEreaFoNRqg@mail.gmail.com>
Date:	Wed, 6 Jan 2016 10:21:33 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	Rohit <rohit.kr@...sung.com>, Laura Abbott <labbott@...hat.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Arve Hjønnevåg <arve@...roid.com>,
	riandrews@...roid.com, gioh.kim@....com,
	Sumit Semwal <sumit.semwal@...aro.org>,
	mitchelh@...eaurora.org,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Rasmus Villemoes <linux@...musvillemoes.dk>,
	shawn.lin@...k-chips.com, sriram@...irs.net.in,
	Staging subsystem List <devel@...verdev.osuosl.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	pintu.k@...sung.com,
	"vishnu.ps@...sung.com" <vishnu.ps@...sung.com>,
	sreenathd@...sung.com, pintu_agarwal@...oo.com, cpgs@...sung.com,
	me.rohit@...e.com
Subject: Re: [PATCH] staging/ion: Add support to get ion handle from dma buf

On Wed, Jan 6, 2016 at 1:06 AM, Dan Carpenter <dan.carpenter@...cle.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/