Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1302964
| From | Linus Torvalds <torvalds@linux-foundation.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] staging/ion: Add support to get ion handle from dma buf |
| Date | 2016-01-06 19:30 +0100 |
| Message-ID | <qO10n-4M5-25@gated-at.bofh.it> (permalink) |
| References | <qNzns-2S7-3@gated-at.bofh.it> <qNEn8-6zZ-7@gated-at.bofh.it> <qNOFP-57m-3@gated-at.bofh.it> <qNSgq-7wa-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Jan 6, 2016 at 1:06 AM, Dan Carpenter <dan.carpenter@oracle.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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] staging/ion: Add support to get ion handle from dma buf Rohit kumar <rohit.kr@samsung.com> - 2016-01-05 14:00 +0100
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf Laura Abbott <labbott@redhat.com> - 2016-01-05 19:20 +0100
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf Rohit <rohit.kr@samsung.com> - 2016-01-06 06:20 +0100
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf Dan Carpenter <dan.carpenter@oracle.com> - 2016-01-06 10:10 +0100
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf Linus Torvalds <torvalds@linux-foundation.org> - 2016-01-06 19:30 +0100
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf Al Viro <viro@ZenIV.linux.org.uk> - 2016-01-06 19:30 +0100
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf Jonathan Corbet <corbet@lwn.net> - 2016-01-06 22:40 +0100
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf Dan Carpenter <dan.carpenter@oracle.com> - 2016-01-07 10:00 +0100
Re: [PATCH] staging/ion: Add support to get ion handle from dma buf Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2016-01-09 05:50 +0100
[PATCHv2 1/1] staging/ion: Add support to get ion handle from dma buf Rohit kumar <rohit.kr@samsung.com> - 2016-01-06 08:10 +0100
Re: [PATCHv2 1/1] staging/ion: Add support to get ion handle from dma buf Laura Abbott <labbott@redhat.com> - 2016-01-06 19:30 +0100
Re: [PATCHv2 1/1] staging/ion: Add support to get ion handle from dma buf Sumit Semwal <sumit.semwal@linaro.org> - 2016-01-07 15:20 +0100
Re: [PATCHv2 1/1] staging/ion: Add support to get ion handle from dma buf Rohit <rohit.kr@samsung.com> - 2016-01-08 08:50 +0100
[PATCHv3 1/1] staging/ion: Add support to get ion handle from dma buf Rohit kumar <rohit.kr@samsung.com> - 2016-01-12 05:00 +0100
csiph-web