From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] glibc: Syscall fixes for mips/risc-v/mucroblaze
Date: Sat, 29 Feb 2020 17:32:19 +0200 [thread overview]
Message-ID: <20200229153219.GA25145@localhost> (raw)
In-Reply-To: <20200229152352.1993520-1-raj.khem@gmail.com>
On Sat, Feb 29, 2020 at 07:23:52AM -0800, Khem Raj wrote:
> Should fix the mips make 4.3 issue on target
>
> Changes in this delta
>
> * 71f2b249a2 malloc/tst-mallocfork2: Kill lingering process for unexpected failures
> * 5d31b083e4 riscv: Avoid clobbering register parameters in syscall
> * f4f8843515 microblaze: Avoid clobbering register parameters in syscall
> * aa638b86b2 mips: Fix argument passing for inlined syscalls on Linux [BZ #25523]
> * ae1b6b13d4 mips: Use 'long int' and 'long long int' in linux syscall code
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/recipes-core/glibc/glibc-version.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/glibc/glibc-version.inc b/meta/recipes-core/glibc/glibc-version.inc
> index f489650f70..f7acf99752 100644
> --- a/meta/recipes-core/glibc/glibc-version.inc
> +++ b/meta/recipes-core/glibc/glibc-version.inc
> @@ -1,6 +1,6 @@
> SRCBRANCH ?= "release/2.31/master"
> PV = "2.31"
> -SRCREV_glibc ?= "9ea3686266dca3f004ba874745a4087a89682617"
> +SRCREV_glibc ?= "71f2b249a28e17eac0e47c53af44d5c5b65101aa"
>...
I have the same locally, but then PV should be "2.31+git${SRCPV}"
and I haven't yet sorted out everything afterwards.
cu
Adrian
prev parent reply other threads:[~2020-02-29 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 15:23 [PATCH] glibc: Syscall fixes for mips/risc-v/mucroblaze Khem Raj
2020-02-29 15:32 ` Adrian Bunk [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=20200229153219.GA25145@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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