Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Norbert Lange <nolange79@gmail.com>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2, 1/1] package/pkg-autotools: fix runtime path
Date: Tue, 2 Aug 2022 23:18:33 +0200	[thread overview]
Message-ID: <20220802231833.6617455e@windsurf> (raw)
In-Reply-To: <CADYdroNPVcCoHyPj7zsufP0JQiaXnYTsPNvze3CsSpW0fPT46w@mail.gmail.com>

On Tue, 2 Aug 2022 12:45:01 +0200
Norbert Lange <nolange79@gmail.com> wrote:

> > Could you try if it does? If so, I think this is OK. We will see how
> > many other packages are affected. If only wipe is affected, fixing wipe
> > is fine. If too many packages are affected, we will have to think of a
> > different solution.  
> 
> Gives alot warnings, but yes, fixes the issue.

Will you send a patch?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-08-02 21:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 15:46 [Buildroot] [PATCH v2, 1/1] package/pkg-autotools: fix runtime path Fabrice Fontaine
2022-07-29 19:58 ` Thomas Petazzoni via buildroot
2022-08-01 16:54 ` Thomas Petazzoni via buildroot
2022-08-02  7:55   ` Norbert Lange
2022-08-02  8:40     ` Thomas Petazzoni via buildroot
2022-08-02  8:49       ` Norbert Lange
2022-08-02  9:39         ` Thomas Petazzoni via buildroot
2022-08-02 10:45           ` Norbert Lange
2022-08-02 21:18             ` Thomas Petazzoni via buildroot [this message]
2022-09-07 15:55       ` Peter Korsgaard
2022-08-11 20:37   ` Thomas Petazzoni via buildroot
2022-08-11 20:44     ` Fabrice Fontaine

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=20220802231833.6617455e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=nolange79@gmail.com \
    --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