From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: yegorslists--- via buildroot <buildroot@buildroot.org>
Cc: Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/python-dtschema: new package
Date: Sun, 7 Aug 2022 14:55:53 +0200 [thread overview]
Message-ID: <20220807145553.023c66ce@windsurf> (raw)
In-Reply-To: <20220804052332.19537-1-yegorslists@googlemail.com>
On Thu, 4 Aug 2022 07:23:31 +0200
yegorslists--- via buildroot <buildroot@buildroot.org> wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> package/Config.in | 1 +
> package/python-dtschema/Config.in | 10 ++++++++++
> package/python-dtschema/python-dtschema.hash | 5 +++++
> package/python-dtschema/python-dtschema.mk | 15 +++++++++++++++
> 4 files changed, 31 insertions(+)
> create mode 100644 package/python-dtschema/Config.in
> create mode 100644 package/python-dtschema/python-dtschema.hash
> create mode 100644 package/python-dtschema/python-dtschema.mk
Thanks, both applied. On the second patch, adding the sample test
script in DEVELOPERS file was missing (the test itself was added, but
not the sample script), so I fixed that up when applying.
Thanks again!
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
prev parent reply other threads:[~2022-08-07 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 5:23 [Buildroot] [PATCH 1/2] package/python-dtschema: new package yegorslists--- via buildroot
2022-08-04 5:23 ` [Buildroot] [PATCH 2/2] support/testing: add test for python-dtschema yegorslists
2022-08-07 12:55 ` 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=20220807145553.023c66ce@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox