From: Dragan Mladjenovic <dmladjenovic@wavecomp.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
"libc-stable@sourceware.org" <libc-stable@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
Siddhesh Poyarekar <siddhesh@sourceware.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: Backport of mips: Force RWX stack for hard-float builds that can run on pre-4.8 kernels
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <5DBBF48E.30706@wavecomp.com> (raw)
In-Reply-To: <87tv7ox28v.fsf@oldenburg2.str.redhat.com>
On 31.10.2019. 18:18, Florian Weimer wrote:
> * Dragan Mladjenovic:
>
>> Sorry for this really late response. I finally managed to get my test
>> machines in order. If it helps, I rechecked old releases and patched
>> ones on 5.3 kernel /-hard-float/-EB/-mabi=o32/n32/n64 w/ and w/o
>> exec-stack by default and there were no new failures. What do I do next?
>> Do I need to get the approval of release manager for each branch
>> individually?
>
> No, if it fixes a bug and does not add symbols, you can backport it on
> your own and commit it. We expect some diligence regarding testing, but
> we have no way of enforcing that.
>
> Thanks,
> Florian
>
But I don't have write access to the glibc repo. I would be grateful if
someone who can do it for me. I can provide patches that apply to each
branch without change if it helps to ease the friction of backporting.
Thanks in advance,
Dragan
next prev parent reply other threads:[~2019-11-01 9:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Dragan Mladjenovic
2019-01-01 0:00 ` Dragan Mladjenovic
2019-01-01 0:00 ` Adhemerval Zanella
2019-01-01 0:00 ` Dragan Mladjenovic
2019-01-01 0:00 ` Florian Weimer
2019-01-01 0:00 ` Dragan Mladjenovic [this message]
2019-01-01 0:00 ` Adhemerval Zanella
2019-01-01 0:00 ` Dragan Mladjenovic
2019-01-01 0:00 ` Adhemerval Zanella
2019-01-01 0:00 ` Adhemerval Zanella
2019-01-01 0:00 ` Dragan Mladjenovic
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=5DBBF48E.30706@wavecomp.com \
--to=dmladjenovic@wavecomp.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=ldv@altlinux.org \
--cc=libc-stable@sourceware.org \
--cc=siddhesh@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).