From: Greg KH <gregkh@linuxfoundation.org>
To: SeongJae Park <sj38.park@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Remove CsrEventHandle and functions using it
Date: Thu, 25 Oct 2012 12:16:22 -0700 [thread overview]
Message-ID: <20121025191622.GA4088@kroah.com> (raw)
In-Reply-To: <1351144271-24443-1-git-send-email-sj38.park@gmail.com>
On Thu, Oct 25, 2012 at 02:51:10PM +0900, SeongJae Park wrote:
> Nobody use CsrEventHandle, Nobody call function using it as parameter.
> So, remove it.
>
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
> ---
> drivers/staging/csr/csr_framework_ext.h | 61 -------------------------
> drivers/staging/csr/csr_framework_ext_types.h | 2 -
> 2 files changed, 63 deletions(-)
This patch applies with fuzz, which implies that you didn't make it
against the latest tree. Care to redo it, and the 2/2 patch, against
either my staging-next branch of the staging.git tree, or the next
linux-next release that will happen tomorrow, and resend them?
thanks,
greg k-h
next prev parent reply other threads:[~2012-10-25 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 5:51 SeongJae Park
2012-10-25 5:51 ` [PATCH 2/2] Remove struct CsrEvent SeongJae Park
2012-10-25 19:16 ` Greg KH [this message]
2012-10-26 3:13 ` [PATCH 1/2] Remove CsrEventHandle and functions using it SeongJae Park
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=20121025191622.GA4088@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj38.park@gmail.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
Powered by JetHome