All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] package/tbtools: bump to version 0.4.1
Date: Wed, 10 Jul 2024 23:45:31 +0200	[thread overview]
Message-ID: <20240710234531.78118499@windsurf> (raw)
In-Reply-To: <20240618130403.3387346-1-mika.westerberg@linux.intel.com>

Hello Mika,

Thanks for the patch. One comment below.

On Tue, 18 Jun 2024 16:04:01 +0300
Mika Westerberg <mika.westerberg@linux.intel.com> wrote:

> Update to the latest release of tbtools.
> 
> This should also get rid of the couple of build errors seen on sparc64
> builds.

We really need more than "should" in commit logs, but guarantees :)

So practically speaking, we do expect you do to test that it fixes
sparc64 builds, and if it does, include a reference to the autobuilder
failures that are being fixed. I adjusted the commit log with the
relevant information when committing:

  https://gitlab.com/buildroot.org/buildroot/-/commit/f5251865413c6a50759d6f48b3300dc1be6122fb

Applied with that change. 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

      parent reply	other threads:[~2024-07-10 21:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 13:04 [Buildroot] [PATCH 1/3] package/tbtools: bump to version 0.4.1 Mika Westerberg
2024-06-18 13:04 ` [Buildroot] [PATCH 2/3] package/tbtools: Install bash completion files and scripts Mika Westerberg
2024-07-10 21:46   ` Thomas Petazzoni via buildroot
2024-06-18 13:04 ` [Buildroot] [PATCH 3/3] package/tbtools: Allow 32-bit builds Mika Westerberg
2024-07-10 21:46   ` Thomas Petazzoni via buildroot
2024-07-10 21:45 ` 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=20240710234531.78118499@windsurf \
    --to=buildroot@buildroot.org \
    --cc=mika.westerberg@linux.intel.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.