From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Philipp Rudo <prudo@linux.ibm.com>,
Hans de Goede <hdegoede@redhat.com>,
Ingo Molnar <mingo@redhat.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Arvind Sankar <nivedita@alum.mit.edu>,
Nathan Chancellor <natechancellor@gmail.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v2 0/1] s390/purgatory: Make sure we fail the build if purgatory has missing symbols
Date: Wed, 9 Oct 2019 16:50:22 +0200 [thread overview]
Message-ID: <ee1e9da7-2f5a-8651-78ba-15398c4ceab6@de.ibm.com> (raw)
In-Reply-To: <20191009113917.47ef6eda@laptop-ibm>
On 09.10.19 11:39, Philipp Rudo wrote:
> Hi Hans,
>
> also adding Ingo on Cc.
>
> I tested you patch on s390 and it does what it's supposed to do. The build now
> fails with
>
> LD arch/s390/purgatory/purgatory.chk
> arch/s390/purgatory/purgatory: In function `sha256_update':
> (.text+0x3bc2): undefined reference to `memzero_explicit'
> /home/prudo/git/linux/linux/arch/s390/purgatory/Makefile:38: recipe for target 'arch/s390/purgatory/purgatory.chk' failed
> make[3]: *** [arch/s390/purgatory/purgatory.chk] Error 1
>
> After applying Arvid's memzero_explizit fix ("[PATCH] lib/string: make
> memzero_explicit inline instead of external") as well the build works again.
>
> My only problem is how to uptream your patch. Just adding it to our branch
> would cause a (intentional) build breakage until Ingo's branch is merged.
>
> @Vasliy & Ingo: Can you please find a solution for this.
I talked quickly to Vasily. The best solution is likely to carry that
patch in the tree that contains the fix. Ingo, can you carry the s390
patch in your tip tree as well?
With my s390 co-maintainer hat on:
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Please also consider Philipps mail as "Tested-by:"
prev parent reply other threads:[~2019-10-09 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 8:54 [RFC v2 0/1] s390/purgatory: Make sure we fail the build if purgatory has missing symbols Hans de Goede
2019-10-08 8:54 ` [RFC v2] " Hans de Goede
2019-10-09 9:39 ` [RFC v2 0/1] " Philipp Rudo
2019-10-09 14:50 ` Christian Borntraeger [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=ee1e9da7-2f5a-8651-78ba-15398c4ceab6@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hdegoede@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=natechancellor@gmail.com \
--cc=nivedita@alum.mit.edu \
--cc=prudo@linux.ibm.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