From: Greg KH <greg@kroah.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the final tree (usb tree related)
Date: Fri, 13 Aug 2010 09:05:48 -0700 [thread overview]
Message-ID: <20100813160548.GA21222@kroah.com> (raw)
In-Reply-To: <AANLkTi=GY7ndsAhe4u0ZjpuGU8Bhh+dUxQt+oaNtvTC0@mail.gmail.com>
On Fri, Aug 13, 2010 at 06:03:49PM +0300, Andy Shevchenko wrote:
> On Fri, Aug 13, 2010 at 5:49 PM, Greg KH <greg@kroah.com> wrote:
> >> After merging the final tree, today's linux-next build (powerpc
> >> allyesconfig) produced these warnings:
> >>
> >> /scratch/sfr/next/drivers/usb/gadget/storage_common.c:718: warning: 'fsg_show_nofua' defined but not used
> >> /scratch/sfr/next/drivers/usb/gadget/storage_common.c:782: warning: 'fsg_store_nofua' defined but not used
> >> /scratch/sfr/next/drivers/usb/gadget/storage_common.c:718: warning: 'fsg_show_nofua' defined but not used
> >> /scratch/sfr/next/drivers/usb/gadget/storage_common.c:782: warning: 'fsg_store_nofua' defined but not used
> >>
> >> Introduced by commit ed4825f7332669779540be27cb263daf22af3b1c ("USB:
> >> gadget: storage: optional SCSI WRITE FUA bit") from the usb tree.
> >
> > Sorry about missing this, I have a patch to fix this up now.
>
> I hope you are talking about last Michal's approach:
> <550ddf8273d87cb418dd5716cbec906e74aa03d4.1281625724.git.m.nazarewicz@samsung.com>
Yes.
prev parent reply other threads:[~2010-08-13 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 4:18 linux-next: build warning after merge of the final tree (usb tree related) Stephen Rothwell
2010-08-13 14:49 ` Greg KH
2010-08-13 15:03 ` Andy Shevchenko
2010-08-13 16:05 ` 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=20100813160548.GA21222@kroah.com \
--to=greg@kroah.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.