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, Dan Streetman <ddstreet@ieee.org>
Subject: Re: linux-next: Tree for Dec 16 (lib/842/842_decompress)
Date: Wed, 16 Dec 2015 12:23:24 -0800 [thread overview]
Message-ID: <5671C83C.7@infradead.org> (raw)
In-Reply-To: <20151216164343.0cb641ce@canb.auug.org.au>
On 12/15/15 21:43, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20151215:
>
> The drm-misc tree gained a conflict against Linus' tree.
>
> The i2c tree gained a build failure for which I applied a patch.
>
> The gpio tree gained a build failure so I used the version from
> next-20151215.
>
on i386, when CONFIG_PRINTK is not enabled:
../lib/842/842_decompress.c: In function '__do_index':
../lib/842/842_decompress.c:205:2: error: implicit declaration of function 'no_printk' [-Werror=implicit-function-declaration]
pr_debug("index%x to %lx off %lx adjoff %lx tot %lx data %lx\n",
^
--
~Randy
next prev parent reply other threads:[~2015-12-16 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 5:43 linux-next: Tree for Dec 16 Stephen Rothwell
2015-12-16 19:28 ` linux-next: Tree for Dec 16 (gpu/drm/vc4) Randy Dunlap
2015-12-17 0:42 ` Eric Anholt
2015-12-16 20:23 ` Randy Dunlap [this message]
2015-12-18 14:32 ` linux-next: Tree for Dec 16 (lib/842/842_decompress) Dan Streetman
2015-12-18 16:08 ` Randy Dunlap
2015-12-21 17:12 ` Dan Streetman
2015-12-21 17:52 ` [PATCH] crypto: 842 - remove WARN inside printk Dan Streetman
2015-12-23 10:25 ` Herbert Xu
2015-12-16 21:05 ` linux-next: Tree for Dec 16 (i2c/busses/i2c-emev2) Randy Dunlap
2015-12-16 21:18 ` Wolfram Sang
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=5671C83C.7@infradead.org \
--to=rdunlap@infradead.org \
--cc=ddstreet@ieee.org \
--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 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).