From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
devel@driverdev.osuosl.org, pintu.k@samsung.com,
me.rohit@live.com, paul.gortmaker@windriver.com,
gregkh@linuxfoundation.org, shawn.lin@rock-chips.com,
linux@rasmusvillemoes.dk, riandrews@android.com,
linux-kernel@vger.kernel.org, Rohit <rohit.kr@samsung.com>,
sriram@marirs.net.in, arve@android.com, cpgs@samsung.com,
gioh.kim@lge.com, sreenathd@samsung.com, pintu_agarwal@yahoo.com,
sumit.semwal@linaro.org, vishnu.ps@samsung.com
Subject: Re: [PATCH] staging/ion: Add support to get ion handle from dma buf
Date: Sat, 9 Jan 2016 10:14:03 +0530 [thread overview]
Message-ID: <20160109044403.GA4662@sudip-pc> (raw)
In-Reply-To: <20160107085734.GJ23363@mwanda>
On Thu, Jan 07, 2016 at 11:57:34AM +0300, Dan Carpenter wrote:
> Hm... Perhaps I should be CC'ing LKML more often. What's the rule on
> this, should I just send bugfixes to LKML and whitespace changes to only
> subsystem list?
All my patches (whitespace, bugfix, build fail) always has CC to lkml.
Infact, I have setup an alias for that so that i don't have to add lkml
manually everytime.
sm = send-email --cc=linux-kernel@vger.kernel.org
regards
sudip
next prev parent reply other threads:[~2016-01-09 4:44 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
2016-01-07 8:57 ` Dan Carpenter
2016-01-09 4:44 ` Sudip Mukherjee [this message]
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=20160109044403.GA4662@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=arve@android.com \
--cc=corbet@lwn.net \
--cc=cpgs@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gioh.kim@lge.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=me.rohit@live.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).