From: Paul Mundt <lethal@linux-sh.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Magnus Damm <damm@igel.co.jp>
Subject: Re: linux-next: sh tree build warning
Date: Tue, 18 Nov 2008 12:42:06 +0900 [thread overview]
Message-ID: <20081118034206.GA23923@linux-sh.org> (raw)
In-Reply-To: <20081117103446.e5c66fec.sfr@canb.auug.org.au>
On Mon, Nov 17, 2008 at 10:34:46AM +1100, Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next build (x86_64 allmodconfig) produced these warning:
>
> drivers/usb/gadget/m66592-udc.c: In function 'm66592_probe':
> drivers/usb/gadget/m66592-udc.c:1672: warning: label 'clean_up2' defined but not used
> drivers/usb/host/r8a66597-hcd.c: In function 'r8a66597_probe':
> drivers/usb/host/r8a66597-hcd.c:2401: warning: label 'clean_up2' defined but not used
>
> Added by commit 985fc7c81c7852f2e104c71cbe913ace683c9e6a ("sh: sh_mobile
> usbf clock framework support").
Fixed, thanks.
prev parent reply other threads:[~2008-11-18 3:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 23:34 linux-next: sh tree build warning Stephen Rothwell
2008-11-18 3:42 ` Paul Mundt [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=20081118034206.GA23923@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=damm@igel.co.jp \
--cc=linux-next@vger.kernel.org \
--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).