public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Colin King <colin.king@canonical.com>
Cc: Johnny Kim <johnny.kim@atmel.com>,
	Austin Shin <austin.shin@atmel.com>,
	Chris Park <chris.park@atmel.com>, Tony Cho <tony.cho@atmel.com>,
	Glen Lee <glen.lee@atmel.com>, Leo Kim <leo.kim@atmel.com>,
	linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wilc1000: remove wilc1000_spi_ops as it is not used
Date: Mon, 15 Feb 2016 18:22:40 -0800	[thread overview]
Message-ID: <20160216022240.GA31825@kroah.com> (raw)
In-Reply-To: <1455549507-25553-1-git-send-email-colin.king@canonical.com>

On Mon, Feb 15, 2016 at 03:18:27PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> building with gcc 6 I hit a build failure:
> 
>   CC      drivers/staging/wilc1000/wilc_spi.o
> drivers/staging/wilc1000/wilc_spi.c:123:34: error: storage size of
>  ‘wilc1000_spi_ops’ isn’t known
>  static const struct wilc1000_ops wilc1000_spi_ops;
>                                   ^~~~~~~~~~~~~~~~
> drivers/staging/wilc1000/wilc_spi.c:123:34: warning: ‘wilc1000_spi_ops’
>   defined but not used [-Wunused-const-variable]
> 
> Since wilc1000_spi_ops is not used, remove it and the driver builds.
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/staging/wilc1000/wilc_spi.c | 2 --
>  1 file changed, 2 deletions(-)

Doesn't apply to my tree at all, are you sure you are using linux-next
for this?

thanks,

greg k-h

      reply	other threads:[~2016-02-16  2:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 15:18 [PATCH] staging: wilc1000: remove wilc1000_spi_ops as it is not used Colin King
2016-02-16  2:22 ` Greg Kroah-Hartman [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=20160216022240.GA31825@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=austin.shin@atmel.com \
    --cc=chris.park@atmel.com \
    --cc=colin.king@canonical.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=glen.lee@atmel.com \
    --cc=johnny.kim@atmel.com \
    --cc=leo.kim@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tony.cho@atmel.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