From: Anil Shashikumar Belur <askb23@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: tklauser@distanz.ch, dan.carpenter@oracle.com, bjorn@mork.no,
silvio.fricke@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: vt6655: ioctl.c - missing __user annotation
Date: Thu, 31 Jul 2014 08:46:58 +0530 [thread overview]
Message-ID: <53D9B52A.2070604@gmail.com> (raw)
In-Reply-To: <20140731000854.GA8934@kroah.com>
On Thursday 31 July 2014 05:38 AM, Greg KH wrote:
>
> This patch doesn't apply against my tree at all, what did you make it
> against?
>
> Always work against linux-next, or the staging-next branch of my
> staging.git tree on git.kernel.org.
>
> thanks,
>
> greg k-h
Hi,
I am working on staging.git. After rebasing with staging-next, git log
shows someone has recently submitted this fix.
Thanks,
Anil
prev parent reply other threads:[~2014-07-31 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 12:59 [PATCH v3] staging: vt6655: ioctl.c - missing __user annotation Anil Belur
2014-07-30 13:26 ` Dan Carpenter
2014-07-31 0:08 ` Greg KH
2014-07-31 3:16 ` Anil Shashikumar Belur [this message]
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=53D9B52A.2070604@gmail.com \
--to=askb23@gmail.com \
--cc=bjorn@mork.no \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=silvio.fricke@gmail.com \
--cc=tklauser@distanz.ch \
/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