Date: Wed, 4 May 2022 17:16:04 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Piotr Kubaj <pkubaj@anongoth.pl> Cc: Emmanuel Vadot <manu@bidouilliste.com>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: ecf09fe34600 - main - graphics/gpu-firmware*-kmod: disable amdgpu on powerpc64 Message-ID: <20220504151604.dxems72xwxhj3eig@aniel.nours.eu> In-Reply-To: <YnKOm%2BJMm4E1AHY%2B@KGPE-D16> References: <202205041257.244CvQYJ029723@gitrepo.freebsd.org> <20220504152200.5881461e1e927b155884fe4c@bidouilliste.com> <YnKOm%2BJMm4E1AHY%2B@KGPE-D16>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 04, 2022 at 04:32:59PM +0200, Piotr Kubaj wrote: > On 22-05-04 15:22:00, Emmanuel Vadot wrote: > > On Wed, 4 May 2022 12:57:26 GMT > > Piotr Kubaj <pkubaj@FreeBSD.org> wrote: > > > > > The branch main has been updated by pkubaj: > > > > > > URL: https://cgit.FreeBSD.org/ports/commit/?id=ecf09fe3460067b442ba41a6adb85897c99442b5 > > > > > > commit ecf09fe3460067b442ba41a6adb85897c99442b5 > > > Author: Piotr Kubaj <pkubaj@FreeBSD.org> > > > AuthorDate: 2022-05-04 12:54:19 +0000 > > > Commit: Piotr Kubaj <pkubaj@FreeBSD.org> > > > CommitDate: 2022-05-04 12:54:19 +0000 > > > > > > graphics/gpu-firmware*-kmod: disable amdgpu on powerpc64 > > > > > > amdgpu has known endianness issues and doesn't work on powerpc64. > > > radeonkms works, while amdgpu works on powerpc64le. > > > --- > > > graphics/gpu-firmware-amd-kmod/Makefile | 4 +- > > > graphics/gpu-firmware-kmod/Makefile | 67 +++++++++++++++++---------------- > > > 2 files changed, 37 insertions(+), 34 deletions(-) > > > > > > > Can you respect MAINTAINER and open a review next time ? > > I believe this falls under tier 2 blanket. Correct me if I'm mistaken. It somehow is and somehow isn't, basically the blanket for tier 2 is to commit trivial changes which allows a port to work (or be flagged as not working on a given architecture) exactly the same as the "just fix it blanket". Intrusive changes should anyway be discussed with the maintainer, and yes it is almost impossible to document what is intrusive from what is not, we have to rely on common sense here, and if one has a doubt, it is cheap to send a mail, open a PR, open a review to the maintainer anyway. The change here does not "fix" anything, so in my opinion, seeking for review and opening a discussion with the maintainer would have been a good idea. As for whether your change is a good idea or not, I will let you discuss that with the maintainer. Best regards, Bapt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220504151604.dxems72xwxhj3eig>