From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, USB list <linux-usb@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 20 (usb/gadget/storage_common.c)
Date: Wed, 20 Nov 2013 10:34:04 -0800 [thread overview]
Message-ID: <528D009C.8020507@infradead.org> (raw)
In-Reply-To: <20131120132847.9321fab265bc5cb0a117c61e@canb.auug.org.au>
On 11/19/13 18:28, Stephen Rothwell wrote:
> Hi all,
>
> Please do *not* add any v3.14 material to linux-next until after
> v3.13-rc1 is released.
>
> Changes since 20131119:
>
on x86_64:
when CONFIG_BLOCK is not enabled:
drivers/usb/gadget/storage_common.c: In function 'fsg_lun_open':
drivers/usb/gadget/storage_common.c:241:3: error: implicit declaration of function 'bdev_logical_block_size' [-Werror=implicit-function-declaration]
drivers/usb/gadget/storage_common.c:242:3: error: implicit declaration of function 'blksize_bits' [-Werror=implicit-function-declaration]
--
~Randy
prev parent reply other threads:[~2013-11-20 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 2:28 linux-next: Tree for Nov 20 Stephen Rothwell
2013-11-20 18:34 ` Randy Dunlap [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=528D009C.8020507@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@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).