From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] powerpc/64: whitelist unresolved modversions CRCs
Date: Thu, 15 Sep 2016 09:41:13 +1000 [thread overview]
Message-ID: <20160915094113.3d4b1777@canb.auug.org.au> (raw)
In-Reply-To: <20160914024507.8759-1-npiggin@gmail.com>
Hi Nick,
On Wed, 14 Sep 2016 12:45:07 +1000 Nicholas Piggin <npiggin@gmail.com> wrote:
>
> These are a symptom of CRC generation failure in generic
> build code, and not powerpc specific.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
OK, so I will use this as a merge fix patch for the kbuild tree today
(instead of the revert I have been doing).
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-09-14 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 2:45 [PATCH] powerpc/64: whitelist unresolved modversions CRCs Nicholas Piggin
2016-09-14 23:41 ` Stephen Rothwell [this message]
2016-09-14 23:49 ` Stephen Rothwell
2016-09-15 4:54 ` Michael Ellerman
2016-09-22 12:48 ` Michal Marek
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=20160915094113.3d4b1777@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmarek@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
/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).