All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org, Antoine Tenart <atenart@kernel.org>,
	Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 2/2] package/swig: bump to version 4.3.0
Date: Mon, 11 Nov 2024 21:19:49 +0100	[thread overview]
Message-ID: <20241111211949.6f844f31@windsurf> (raw)
In-Reply-To: <20241110193734.1463141-2-james.hilliard1@gmail.com>

Hello James,

On Sun, 10 Nov 2024 12:37:34 -0700
James Hilliard <james.hilliard1@gmail.com> wrote:

> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
>  package/swig/swig.hash | 2 +-
>  package/swig/swig.mk   | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)

Thanks for this patch. Could you provide some details on how well you
tested the reverse dependencies of host-swig?

Based on your PATCH 1/2, you tested libselinux, but what about the
other packages? I certainly don't require testing *all* of them, but
since this bump has caused some breakage for libselinux, we can
potentially expect some breakage for other packages. Could you build a
defconfig with a good number of reverse dependencies enabled, and
verify it builds OK, and report this in the commit log?

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-11-11 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 19:37 [Buildroot] [PATCH v2 1/2] package/libselinux: fix swig 4.3.0 compatibility James Hilliard
2024-11-10 19:37 ` [Buildroot] [PATCH v2 2/2] package/swig: bump to version 4.3.0 James Hilliard
2024-11-11 20:19   ` Thomas Petazzoni via buildroot [this message]
2024-11-11 20:25     ` James Hilliard
2024-11-11 20:44       ` 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=20241111211949.6f844f31@windsurf \
    --to=buildroot@buildroot.org \
    --cc=atenart@kernel.org \
    --cc=james.hilliard1@gmail.com \
    --cc=marcus.folkesson@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.