From: Stephen Boyd <stephen.boyd@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 16 (linux/firmware.h)
Date: Thu, 16 Jun 2016 11:12:47 -0700 [thread overview]
Message-ID: <146610076777.8942.6261908779926362192@sboyd-linaro> (raw)
In-Reply-To: <5762D7F3.50802@infradead.org>
Quoting Randy Dunlap (2016-06-16 09:46:43)
> [adding Stephen Boyd]
>
> On 06/16/16 08:02, Randy Dunlap wrote:
> > On 06/15/16 22:49, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Changes since 20160615:
> >>
> >
> > on i386 and/or x86_64:
> >
> > In file included from ../drivers/fpga/fpga-mgr.c:21:0:
> > ../include/linux/firmware.h:82:1: error: expected identifier or ( before { token
> > {
> > ^
> >
> >
>
> See:
>
> static inline int request_firmware_into_buf(const struct firmware **firmware_p,
> const char *name, struct device *device, void *buf, size_t size);
> {
> return -EINVAL;
> }
>
Urgh sorry about that. The semicolon should go away. Andrew can you
squash this in? I tested compilation without this config enabled.
---8<---
diff --git a/include/linux/firmware.h b/include/linux/firmware.h
index bdc24ee92823..b1f9f0ccb8ac 100644
--- a/include/linux/firmware.h
+++ b/include/linux/firmware.h
@@ -78,7 +78,7 @@ static inline int request_firmware_direct(const struct firmware **fw,
}
static inline int request_firmware_into_buf(const struct firmware **firmware_p,
- const char *name, struct device *device, void *buf, size_t size);
+ const char *name, struct device *device, void *buf, size_t size)
{
return -EINVAL;
}
prev parent reply other threads:[~2016-06-16 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 5:49 linux-next: Tree for Jun 16 Stephen Rothwell
2016-06-16 15:02 ` linux-next: Tree for Jun 16 (linux/firmware.h) Randy Dunlap
2016-06-16 16:46 ` Randy Dunlap
2016-06-16 18:12 ` Stephen Boyd [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=146610076777.8942.6261908779926362192@sboyd-linaro \
--to=stephen.boyd@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®