From: Jonathan Corbet <corbet@lwn.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Rohit <rohit.kr@samsung.com>, Laura Abbott <labbott@redhat.com>,
gregkh@linuxfoundation.org, arve@android.com,
riandrews@android.com, gioh.kim@lge.com, sumit.semwal@linaro.org,
mitchelh@codeaurora.org, paul.gortmaker@windriver.com,
linux@rasmusvillemoes.dk, shawn.lin@rock-chips.com,
sriram@marirs.net.in, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, pintu.k@samsung.com,
vishnu.ps@samsung.com, sreenathd@samsung.com,
pintu_agarwal@yahoo.com, cpgs@samsung.com, me.rohit@live.com
Subject: Re: [PATCH] staging/ion: Add support to get ion handle from dma buf
Date: Wed, 6 Jan 2016 14:38:21 -0700 [thread overview]
Message-ID: <20160106143821.2660d02e@lwn.net> (raw)
In-Reply-To: <20160106090622.GG23363@mwanda>
On Wed, 6 Jan 2016 12:06:22 +0300
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> It's not really necessary to CC linux-kernel. No one reads it.
I have to take issue with this too; more of us read it than you might
think. The fact that we're probably all crazy doesn't really figure into
it. Think of linux-kernel as the blockchain of kernel development; it's
a messy thing that takes a lot of resources to maintain (and keep up
with), but when you need to see what happened (or is happening) it's
invaluable.
jon
next prev parent reply other threads:[~2016-01-06 21:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 13:03 [PATCH] staging/ion: Add support to get ion handle from dma buf Rohit kumar
2016-01-05 18:12 ` Laura Abbott
2016-01-06 5:25 ` Rohit
2016-01-06 9:06 ` Dan Carpenter
2016-01-06 18:21 ` Linus Torvalds
2016-01-06 18:24 ` Al Viro
2016-01-06 21:38 ` Jonathan Corbet [this message]
2016-01-07 8:57 ` Dan Carpenter
2016-01-09 4:44 ` Sudip Mukherjee
2016-01-06 7:11 ` [PATCHv2 1/1] " Rohit kumar
2016-01-06 18:26 ` Laura Abbott
2016-01-07 14:13 ` Sumit Semwal
2016-01-08 7:51 ` Rohit
2016-01-12 4:01 ` [PATCHv3 " Rohit kumar
2016-02-01 7:59 ` Rohit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160106143821.2660d02e@lwn.net \
--to=corbet@lwn.net \
--cc=arve@android.com \
--cc=cpgs@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gioh.kim@lge.com \
--cc=gregkh@linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=me.rohit@live.com \
--cc=mitchelh@codeaurora.org \
--cc=paul.gortmaker@windriver.com \
--cc=pintu.k@samsung.com \
--cc=pintu_agarwal@yahoo.com \
--cc=riandrews@android.com \
--cc=rohit.kr@samsung.com \
--cc=shawn.lin@rock-chips.com \
--cc=sreenathd@samsung.com \
--cc=sriram@marirs.net.in \
--cc=sumit.semwal@linaro.org \
--cc=vishnu.ps@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.