Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	linux-amarula@amarulasolutions.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/sunxi-mali-utgard-driver: fix patch fuzz
Date: Thu, 11 Jul 2024 10:52:00 +0200	[thread overview]
Message-ID: <20240711105200.292f5783@windsurf> (raw)
In-Reply-To: <20240711070525.1406612-1-dario.binacchi@amarulasolutions.com>

Hello,

+Arnout in Cc.

On Thu, 11 Jul 2024 09:05:25 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:

> Commit 8f88a644ed7d6 ("support/scripts/apply-patches.sh: set the maximum
> fuzz factor to 0") reduced the fuzz factor.
> 
> Due to this change, sunxi-mali-utgard-driver fails to build with output:
> 
>     - r6p2:
> 
>         Applying 0018-mali-support-building-against-4.20.patch using series:
> 	patching file src/devicedrv/mali/linux/mali_kernel_linux.c
> 	Hunk #1 succeeded at 1125 (offset 193 lines).
> 	patching file src/devicedrv/mali/linux/mali_kernel_linux.h
> 	Hunk #1 FAILED at 16.
> 	Hunk #2 succeeded at 33 (offset 5 lines).
> 	1 out of 2 hunks FAILED -- saving rejects to file src/devicedrv/mali/linux/mali_kernel_linux.h.rej
> 
>     -r8p1:
> 
> 	Applying r6p2/0013-mali-support-building-against-4.15.patch using series:
> 	patching file src/devicedrv/mali/common/mali_control_timer.c
> 	patching file src/devicedrv/mali/common/mali_group.c
> 	Hunk #2 FAILED at 1768.
> 	1 out of 2 hunks FAILED -- saving rejects to file src/devicedrv/mali/common/mali_group.c.rej
> 	patching file src/devicedrv/mali/common/mali_osk_types.h
> 	patching file src/devicedrv/mali/linux/mali_memory_os_alloc.c
> 	Hunk #1 succeeded at 202 (offset -2 lines).
> 	patching file src/devicedrv/mali/linux/mali_osk_timers.c
> 
> 	Applying 0020-mali-support-building-against-4.17.patch using series:
> 	patching file src/devicedrv/mali/linux/mali_memory.c
> 	Hunk #1 FAILED at 57.
> 	1 out of 1 hunk FAILED -- saving rejects to file src/devicedrv/mali/linux/mali_memory.c.rej
> 
> This commit fixes the driver patches on the current package version.
> 
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
>  ...he-patches-to-be-applied-with-fuzz-0.patch | 317 ++++++++++++++++++
>  1 file changed, 317 insertions(+)
>  create mode 100644 package/sunxi-mali-utgard-driver/0002-Update-the-patches-to-be-applied-with-fuzz-0.patch

Thanks for the patch, but I'm not entirely sure that's how we want to
fix this issue. Indeed, apply-patches is used in quite a lot of
packages to apply patches from Debian. Do we want to fix all those
patches, like you did for the sunxi-mali-utgard-driver? I'm not sure.

So in the end, I'm wondering if apply-patches.sh shouldn't take an
argument that specifies whether we accept fuzz or not. We shouldn't
accept fuzz for patches provided by Buildroot itself, but perhaps we
should keep accepting fuzz for patches that are not part of Buildroot.

Arnout, since you accepted the patch changing the apply-patches.sh
behavior, what is your opinion on this?

Best regards,

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-11  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11  7:05 [Buildroot] [PATCH 1/1] package/sunxi-mali-utgard-driver: fix patch fuzz Dario Binacchi
2024-07-11  8:52 ` Thomas Petazzoni via buildroot [this message]
2024-07-11  9:51   ` Arnout Vandecappelle via buildroot
2024-07-11 10:04     ` Thomas Petazzoni via buildroot
2024-07-11 10:21       ` Arnout Vandecappelle via buildroot
2024-07-11 10:28       ` Dario Binacchi
2024-07-11 19:15     ` [Buildroot] [PATCH] package/sunxi-mali-utgard-driver: bump to version 2024-07-11 Giulio Benetti
2024-07-12  7:09       ` Thomas Petazzoni via buildroot
2024-07-12 10:43         ` Giulio Benetti
2024-07-12 11:10           ` Thomas Petazzoni via buildroot
2024-07-12 11:02       ` 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=20240711105200.292f5783@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=linux-amarula@amarulasolutions.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