public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: john.stultz@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpu: ion: fix sparse non static symbol warnings
Date: Tue, 11 Feb 2014 12:25:47 -0800	[thread overview]
Message-ID: <20140211202547.GA11684@kroah.com> (raw)
In-Reply-To: <2249537.0tqhh5qnLv@daeseok-laptop.cloud.net>

On Mon, Feb 10, 2014 at 09:32:22AM +0900, Daeseok Youn wrote:
> >From 08b77be03927d450810c07d3a4440dc8c32fe766 Mon Sep 17 00:00:00 2001
> From: Daeseok Youn <daeseok.youn@gmail.com>
> Date: Mon, 10 Feb 2014 09:02:26 +0900
> Subject: [PATCH] gpu: ion: fix sparse non static symbol warnings
> 
> Fixes the following sparse warnings:
> 
> drivers/staging/android/ion/ion_dummy_driver.c:26:19:
>  warning: symbol 'idev' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:27:17:
>  warning: symbol 'heaps' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:29:6:
>  warning: symbol 'carveout_ptr' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:30:6:
>  warning: symbol 'chunk_ptr' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:32:26:
>  warning: symbol 'dummy_heaps' was not declared. Should it be static?
> drivers/staging/android/ion/ion_dummy_driver.c:59:26:
>  warning: symbol 'dummy_ion_pdata' was not declared. Should it be static?
> 
> Signed-off-by: Daeseok Youn <daeseok.youn@gmail.com>

This patch has already been made in my tree, please always work against
linux-next to prevent duplication of work.

thanks,

greg k-h

      reply	other threads:[~2014-02-11 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10  0:32 [PATCH] gpu: ion: fix sparse non static symbol warnings Daeseok Youn
2014-02-11 20:25 ` Greg KH [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=20140211202547.GA11684@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daeseok.youn@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    /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