From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] kvm: Fix Nix build failure by moving -fno-stack-protector to CFLAGS
Date: Wed, 20 Sep 2023 09:56:35 +0200 [thread overview]
Message-ID: <20230920075635.GA281462@pevik> (raw)
In-Reply-To: <87sf79ffw9.fsf@suse.de>
Hi Richie,
> Hello,
> Martin Doucha <mdoucha@suse.cz> writes:
> > Hi,
> > pvorel should have a look whether it doesn't break the other systems
> > where -fno-stack-protector is needed, but otherwise:
> > Reviewed-by: Martin Doucha <mdoucha@suse.cz>
> Compilation appears to be fine:
> https://github.com/richiejp/ltp/actions/runs/6232857602/job/16916865952
> The tests just TCONF on my hardware, but I guess the risk of breaking
> the test at runtime is low?
I'll test tonight Buildroot toolchains, which usually find errors which aren't
spot by our github CI.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-20 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:38 [LTP] [PATCH] kvm: Fix Nix build failure by moving -fno-stack-protector to CFLAGS Richard Palethorpe via ltp
2023-09-19 12:51 ` Martin Doucha
2023-09-20 7:41 ` Richard Palethorpe
2023-09-20 7:56 ` Petr Vorel [this message]
2023-09-22 7:56 ` Petr Vorel
2023-09-22 8:20 ` Richard Palethorpe
2023-09-22 9:03 ` Petr Vorel
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=20230920075635.GA281462@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.