From: "Alexandre Belloni" <alexandre.belloni@bootlin.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] binutils: Upgrade to 2.37 branch
Date: Thu, 22 Jul 2021 23:37:59 +0200 [thread overview]
Message-ID: <YPnlN0HaML6IFFLy@piout.net> (raw)
In-Reply-To: <CAMKF1soNY99BuAgNxgj7U=FukWY14VUa+_axra0zLB1bqe9u3A@mail.gmail.com>
On 22/07/2021 07:56:11-0700, Khem Raj wrote:
> On Thu, Jul 22, 2021 at 1:22 AM Alexandre Belloni <
> alexandre.belloni@bootlin.com> wrote:
>
> > Hi Khem,
> >
> > On 20/07/2021 19:11:08-0700, Khem Raj wrote:
> > > This izOs next/latest release branch for binutils
> > > Drop backports and CVE fixes which already are applied upstream
> > >
> > > bfd_stdint.h has been removed in favor of using stdint.h
> > >
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > ---
> > > V2: Fixes SDK builds for mingw and glew build with GLES
> > >
> >
> > This didn't apply properly, I fixed it up, can you check
> >
> > https://git.openembedded.org/openembedded-core-contrib/commit/?h=abelloni/master-next&id=efb06e3e03c750944bfa40314dae70c054bdaed4
> >
>
> What portion did not apply ? It looks alright to me but want to know so I
> can correct my branch since I have few other patches lined up before it I
> wonder if that’s the issue or something else
Almost none of it applied, it is most likely caused by whitespace
changes as this was the main difference between v1 and v2. What I did is
take v1 and changed the SRCREV to be the one of v2.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-22 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 2:11 [PATCH v2] binutils: Upgrade to 2.37 branch Khem Raj
2021-07-22 8:22 ` [OE-core] " Alexandre Belloni
2021-07-22 14:56 ` Khem Raj
2021-07-22 21:37 ` Alexandre Belloni [this message]
2021-07-23 0:04 ` Khem Raj
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=YPnlN0HaML6IFFLy@piout.net \
--to=alexandre.belloni@bootlin.com \
--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 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.