Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/elf2flt: handle more relocations
Date: Mon, 7 Aug 2023 10:42:40 +0200	[thread overview]
Message-ID: <ZNCugJjbSzNv7YPd@waldemar-brodkorb.de> (raw)
In-Reply-To: <20230807101431.40cb9d54@windsurf>

Hi Thomas,
Thomas Petazzoni wrote,

> Hello,
> 
> On Mon, 7 Aug 2023 09:50:20 +0200
> Waldemar Brodkorb <wbx@openadk.org> wrote:
> 
> > Fixes following autobuild failure:
> > http://autobuild.buildroot.net/results/c16/c161f191d85f9d064626ee6fcfebea61d916e434/
> > 
> > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> > ---
> >  ...e-relocations-required-to-be-handled.patch | 39 +++++++++++++++++++
> >  1 file changed, 39 insertions(+)
> >  create mode 100644 package/elf2flt/0008-riscv64-add-more-relocations-required-to-be-handled.patch
> > 
> > diff --git a/package/elf2flt/0008-riscv64-add-more-relocations-required-to-be-handled.patch b/package/elf2flt/0008-riscv64-add-more-relocations-required-to-be-handled.patch
> > new file mode 100644
> > index 0000000000..c619a1d068
> > --- /dev/null
> > +++ b/package/elf2flt/0008-riscv64-add-more-relocations-required-to-be-handled.patch
> > @@ -0,0 +1,39 @@
> > +From 5acfed0012f2fff9801b25403bd8a5e1c2ccfea2 Mon Sep 17 00:00:00 2001
> > +From: Waldemar Brodkorb <wbx@openadk.org>
> > +Date: Mon, 7 Aug 2023 09:30:34 +0200
> > +Subject: [PATCH 8/8] riscv64: add more relocations required to be handled
> > +
> > +Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> 
> Thanks for the patch. However, it will raise at least two warnings from
> "make check-package":
> 
> (1) Because it has 8/8, but we don't want such numbering in Buildroot patches
> 
> (2) Because it lacks an Upstream: tag
> 
> Could you address those details? Especially the Upstream: tag means we
> expect this patch to have been submitted upstream.

The problem with upstreaming the patch is, that it depends on not
yet included patches for riscv64 noMMU. How should I proceed here?

best regards
 Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-08-07  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  7:50 [Buildroot] [PATCH] package/elf2flt: handle more relocations Waldemar Brodkorb
2023-08-07  8:14 ` Thomas Petazzoni via buildroot
2023-08-07  8:42   ` Waldemar Brodkorb [this message]
2023-08-07  8:49     ` Thomas Petazzoni via buildroot

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=ZNCugJjbSzNv7YPd@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.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