public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: venkata.pyla@toshiba-tsip.com, isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/2] Fix reproducible issues in armhf
Date: Tue, 15 Aug 2023 17:59:32 +0300	[thread overview]
Message-ID: <c9855b5d8eb01149e93cbcfcf92d6f0de0874ff9.camel@ilbers.de> (raw)
In-Reply-To: <20230809134703.8475-1-venkata.pyla@toshiba-tsip.com>

On Wed, 2023-08-09 at 19:17 +0530, venkata.pyla@toshiba-tsip.com wrote:
> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
> 
> Hi,
> 
> Updated the patch series based on the feedback.
> 
> v2 changes:
>  - Drop cleaning of blkid cache files in rootfs_postporcess_command
> and
>    do it in rootfs_finalize method.
>  - corrected the condition for scanning the *.core files
> 
> venkata pyla (2):
>   image.bbclass: remove core files generated in rootfs
>   image.bbclass: clean blkid cache files from rootfs
> 
>  meta/classes/image.bbclass | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> -- 
> 2.20.1
> 
> 

Applied to next, thanks.

  parent reply	other threads:[~2023-08-15 14:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 16:35 [PATCH " venkata.pyla
2023-08-07 16:35 ` [PATCH 1/2] rootfs.bbclass: clean blkid cache files from rootfs venkata.pyla
2023-08-07 16:58   ` vijai kumar
2023-08-09  4:05     ` Venkata.Pyla
2023-08-09 13:47       ` [PATCH v2 0/2] Fix reproducible issues in armhf venkata.pyla
2023-08-14 11:57         ` vijai kumar
2023-08-15 14:59         ` Uladzimir Bely [this message]
2023-08-09 13:47       ` [PATCH v2 1/2] image.bbclass: remove core files generated in rootfs venkata.pyla
2023-08-09 13:47       ` [PATCH v2 2/2] image.bbclass: clean blkid cache files from rootfs venkata.pyla
2023-08-31  6:16     ` [PATCH 1/2] rootfs.bbclass: " MOESSBAUER, Felix
2023-08-07 16:35 ` [PATCH 2/2] image.bbclass: remove core files generated in rootfs venkata.pyla
2023-08-31  6:21   ` MOESSBAUER, Felix

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=c9855b5d8eb01149e93cbcfcf92d6f0de0874ff9.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=venkata.pyla@toshiba-tsip.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