linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michal Kazior <michal@plume.com>, Pavel Machek <pavel@ucw.cz>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: linux-next: build warning after merge of the leds tree
Date: Thu, 14 Feb 2019 22:13:45 +0100	[thread overview]
Message-ID: <a741b99c-83ff-547b-90d6-f54f8f7de966@gmail.com> (raw)
In-Reply-To: <20190214144610.3672e9d7@canb.auug.org.au>

Hi Stephen and all,

On 2/14/19 4:46 AM, Stephen Rothwell wrote:
> Hi Jacek,
> 
> After merging the leds tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
> 
> drivers/leds/leds-lp55xx-common.c: In function 'lp55xx_firmware_loaded':
> drivers/leds/leds-lp55xx-common.c:217:1: warning: label 'out' defined but not used [-Wunused-label]
>   out:
>   ^~~

Thank you for the heads-up. It's my bad - I didn't use sparse on it.

Fixed up the original patch.

> Introduced by commit
> 
>    905c2157dd19 ("leds: lp55xx: fix null deref on firmware load failure")
> 

-- 
Best regards,
Jacek Anaszewski

  parent reply	other threads:[~2019-02-14 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  3:46 linux-next: build warning after merge of the leds tree Stephen Rothwell
2019-02-14  7:51 ` Michal Kazior
2019-02-14 21:13 ` Jacek Anaszewski [this message]
2019-03-19  2:58 Stephen Rothwell
2019-03-19 19:53 ` Jacek Anaszewski

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=a741b99c-83ff-547b-90d6-f54f8f7de966@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=anders.roxell@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=michal@plume.com \
    --cc=pavel@ucw.cz \
    --cc=sfr@canb.auug.org.au \
    /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).