All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Saeed Kazemi <kazemi.ms@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/parsec: new package
Date: Mon, 22 Jul 2024 14:13:48 +0200	[thread overview]
Message-ID: <20240722141348.18756600@windsurf> (raw)
In-Reply-To: <20240721183223.2792367-1-kazemi.ms@gmail.com>

Hello Saaed,

On Sun, 21 Jul 2024 20:32:23 +0200
Saeed Kazemi <kazemi.ms@gmail.com> wrote:

> Hardware/platform abstraction service for TPMs, HSMs, and Root of Trust
> 
> https://github.com/parallaxsecond/parsec.git
> 
> Signed-off-by: Saeed Kazemi <kazemi.ms@gmail.com>

Thanks for this patch. Two questions below.

> +Subject: [PATCH] Fix compile errors with latest Rust version
> +
> +Upstream: N/A not applicable directly but based on:
> +https://github.com/parallaxsecond/parsec/commit/82320d345e08fe6310b684191151c78fc5648693

Why are you saying N/A (not applicable), if in fact your change is a
partial backport of an upstream commit? If it's a partial backport,
just state it so:

Upstream: partial backport
of https://github.com/parallaxsecond/parsec/commit/82320d345e08fe6310b684191151c78fc5648693

> +PARSEC_VERSION = 1.3.0

Why 1.3.0 and not 1.4.0 or 1.4.1 that contain the
82320d345e08fe6310b684191151c78fc5648693 fix already ?

Thanks,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-22 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 18:32 [Buildroot] [PATCH 1/1] package/parsec: new package Saeed Kazemi
2024-07-22 12:13 ` Thomas Petazzoni via buildroot [this message]
2024-07-23  7:08   ` Saeed Kazemi
  -- strict thread matches above, loose matches on Subject: below --
2024-07-23  7:04 Saeed Kazemi
2025-01-05 17:15 ` Julien Olivain

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=20240722141348.18756600@windsurf \
    --to=buildroot@buildroot.org \
    --cc=kazemi.ms@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.