All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Gregory Dymarek <gregd72002@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/gengetopt: fix patch fuzz
Date: Sun, 21 Jul 2024 18:21:10 +0200	[thread overview]
Message-ID: <20240721182110.03f3e2a6@windsurf> (raw)
In-Reply-To: <20240720213347.1740848-1-fontaine.fabrice@gmail.com>

On Sat, 20 Jul 2024 23:33:47 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Use upstream patch to fix patch fuzz and avoid the following build
> failure raised since commit 8f88a644ed7d6c9ea55fd4fbe9d7f37055920016
> which reduced the fuzz factor:
> 
> Applying 0001-configure.ac-add-disable-doc-option.patch using patch:
> patching file Makefile.am
> Hunk #1 FAILED at 18.
> 1 out of 1 hunk FAILED -- saving rejects to file Makefile.am.rej
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/4cfa513e024ea2cb2058fde4ffdd727bd379dae7
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  .checkpackageignore                                 |  1 -
>  .../0001-configure.ac-add-disable-doc-option.patch  | 13 +++++++------
>  2 files changed, 7 insertions(+), 7 deletions(-)

Applied to master, thanks.

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

      reply	other threads:[~2024-07-21 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20 21:33 [Buildroot] [PATCH 1/1] package/gengetopt: fix patch fuzz Fabrice Fontaine
2024-07-21 16:21 ` Thomas Petazzoni via buildroot [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=20240721182110.03f3e2a6@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=gregd72002@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 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.