Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Andy Yan <andyshrk@gmail.com>,
	Andy Yan <andyshrk@163.com>, Aaron Sierra <aaron@bubbl-tek.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/iotools: Update to v1.8
Date: Mon, 11 Nov 2024 09:17:00 +0200	[thread overview]
Message-ID: <ZzGvbJyygHw-rQAb@smile.fi.intel.com> (raw)
In-Reply-To: <e097e9606bcd844e440d8cd95e2d494a@free.fr>

On Fri, Nov 08, 2024 at 10:58:24PM +0100, Julien Olivain wrote:
> Hi Andy, all,
> 
> On 06/11/2024 19:48, Andy Shevchenko wrote:
> > This is minor update to iotools to fix some issues Aaron noticed and
> > addressed. The bigger change will come later with better integration
> > with the regular build systems (CMake).
> > 
> > Cc: Aaron Sierra <aaron@bubbl-tek.com>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Applied to master, thanks!
> 
> The patch was not applying as is, as the version number in the Buildroot
> tree does not have the "v". This is for the release monitoring, for new
> release notifications:
> https://release-monitoring.org/project/375158
> 
> Since the modification was trivial, I fixed it while applying.

I see, thanks!

-- 
With Best Regards,
Andy Shevchenko


_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-11-11  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 18:48 [Buildroot] [PATCH v1 1/1] package/iotools: Update to v1.8 Andy Shevchenko
2024-11-06 19:20 ` Jarkko Sakkinen via buildroot
2024-11-08 21:58 ` Julien Olivain
2024-11-11  7:17   ` Andy Shevchenko [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=ZzGvbJyygHw-rQAb@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=aaron@bubbl-tek.com \
    --cc=andyshrk@163.com \
    --cc=andyshrk@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    /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