Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Dario Binacchi <dario.binacchi@amarulasolutions.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 12:04:39 +0200	[thread overview]
Message-ID: <20240711120439.3c5eb010@windsurf> (raw)
In-Reply-To: <29a51211-e273-4b28-ba3c-648df58b83c3@mind.be>

Hello Arnout,

On Thu, 11 Jul 2024 11:51:11 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

> > 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.  
> 
>   AFAIK, Debian patches should apply without fuzz (unless we do stupid stuff 
> like applying our own patches first).

Is this "should" based on actual experimentation/validation, or just
some general assumption?

>   I think this is the only case where we are downloading patches that have 
> incorrect fuzz - or did you encounter any other case, Dario?
> 
>   And in this specific case, upstream is Giulio, so I expect that the PR will be 
> accepted soon and we can simply bump.

Ah, I didn't realize we had an active upstream for this package.
Indeed, it means we will be able to drop our patch.

>   I agree, but only if we actually encounter a situation where this is the case. 
> Note that the implementation will not be super trivial (will require something 
> like FOO_APPLY_PATCHES_FUZZ).

Well, no, I was assuming $(APPLY_PATCHES) that is used in packages
would default to accepting fuzz, and only the $(APPLY_PATCHES) call in
our package infra, which applies our patches, would pass an option to
disable fuzz.

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:[~2024-07-11 10:04 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
2024-07-11  9:51   ` Arnout Vandecappelle via buildroot
2024-07-11 10:04     ` Thomas Petazzoni via buildroot [this message]
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=20240711120439.3c5eb010@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --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