From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <keescook@chromium.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Geliang Tang <geliangtang@163.com>
Subject: Re: linux-next: build failure after merge of the pstore tree
Date: Thu, 2 Jun 2016 14:03:07 +1000 [thread overview]
Message-ID: <20160602140307.506b98ba@canb.auug.org.au> (raw)
In-Reply-To: <20160602102556.722ad0cf@canb.auug.org.au>
Hi Kees,
On Thu, 2 Jun 2016 10:25:56 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the pstore tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/acpi/apei/erst.c:943:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
> .read = erst_reader,
> ^
This also affected arch/powerpc/kernel/nvram_64.c:
arch/powerpc/kernel/nvram_64.c:563:10: error: initialization
from incompatible pointer type [-Werror=incompatible-pointer-types]
.read = nvram_pstore_read,
^
So I added this patch as well:
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 2 Jun 2016 13:58:25 +1000
Subject: [PATCH] pstore: update arch/powerpc/kernel/nvram_64.c for struct pstore_info change
Fixes: d8aaf3511a13 ("pstore: add lzo/lz4 compression support")
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
arch/powerpc/kernel/nvram_64.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/nvram_64.c b/arch/powerpc/kernel/nvram_64.c
index 856f9a7944cd..5ad2579e2cdc 100644
--- a/arch/powerpc/kernel/nvram_64.c
+++ b/arch/powerpc/kernel/nvram_64.c
@@ -444,7 +444,8 @@ static int nvram_pstore_write(enum pstore_type_id type,
*/
static ssize_t nvram_pstore_read(u64 *id, enum pstore_type_id *type,
int *count, struct timespec *time, char **buf,
- bool *compressed, struct pstore_info *psi)
+ bool *compressed, ssize_t *ecc_notice_size,
+ struct pstore_info *psi)
{
struct oops_log_info *oops_hdr;
unsigned int err_type, id_no, size = 0;
--
2.8.1
I guess I don't really know if there is further fixes necessary, these
patches just fix up the build.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-06-02 4:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 0:25 linux-next: build failure after merge of the pstore tree Stephen Rothwell
2016-06-02 2:15 ` Kees Cook
2016-06-02 2:29 ` Stephen Rothwell
2016-06-02 4:03 ` Stephen Rothwell [this message]
2016-06-02 18:14 ` Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2018-08-03 1:00 Stephen Rothwell
2018-08-03 2:56 ` Kees Cook
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=20160602140307.506b98ba@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=geliangtang@163.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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