From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Tal Lubko <tallubko@yahoo.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/chipsec: new package
Date: Fri, 1 Oct 2021 16:40:45 +0200 [thread overview]
Message-ID: <20211001164045.74dfe4d1@windsurf> (raw)
In-Reply-To: <212347867.858114.1633098903235@mail.yahoo.com>
Hello,
On Fri, 1 Oct 2021 14:35:03 +0000 (UTC)
Tal Lubko <tallubko@yahoo.com> wrote:
> I've submitted a patch which adds new package - chipsec, which is a framework for analyzing the security of PC platforms.
> I haven't got a reply for this patch so I've got a feeling I've done something wrong.Have I?
No, you have not. You just need to give some time for the community to
review your patch. The current backlog of patches is ~390 patches to
review, which explains why not all patches receive immediate attention.
As long as you can see your patch at
https://patchwork.ozlabs.org/project/buildroot/list/ it means that it
hasn't been forgotten.
In any case, thanks a lot for your contribution!
Best regards,
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
next prev parent reply other threads:[~2021-10-01 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211001015433.11176-1-tallubko.ref@yahoo.com>
2021-10-01 1:54 ` [Buildroot] [PATCH 1/1] package/chipsec: new package Tal Lubko via buildroot
2021-10-01 14:35 ` Tal Lubko via buildroot
2021-10-01 14:40 ` Thomas Petazzoni [this message]
2021-11-01 15:55 ` Tal Lubko via buildroot
2021-10-12 20:07 ` Arnout Vandecappelle
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=20211001164045.74dfe4d1@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=tallubko@yahoo.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