devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/6] More pylibfdt updates
Date: Fri, 12 Nov 2021 17:10:49 +1100	[thread overview]
Message-ID: <YY4FabtkB6eis8QM@yekko> (raw)
In-Reply-To: <20211112041633.741598-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

On Thu, Nov 11, 2021 at 10:16:27PM -0600, Rob Herring wrote:
> Another batch of pylibfdt updates. This series updates the README for 
> installing, adds metadata for packaging, and reworks the tests to be 
> able to run standalone using python test programs (pytest and tox).
> 
> A test package is uploaded here:
> https://test.pypi.org/project/libfdt/


1..2 applied.  I have some questions about 3.

> 
> Rob
> 
> Rob Herring (6):
>   README: Update pylibfdt install instructions
>   pylibfdt: Add packaging metadata
>   pylibfdt_tests: Don't depend on built dtbs
>   tests: rename pylibfdt_tests.py to test_pylibfdt.py
>   pylibfdt: Include tests and test data in packaging
>   pylibfdt: Add tox support
> 
>  MANIFEST.in                                   |  7 ++++++
>  README                                        | 24 ++++++++++++-------
>  setup.py                                      | 17 +++++++++++++
>  tests/run_tests.sh                            |  3 +--
>  tests/{pylibfdt_tests.py => test_pylibfdt.py} | 22 ++++++++++-------
>  tox.ini                                       |  6 +++++
>  6 files changed, 60 insertions(+), 19 deletions(-)
>  rename tests/{pylibfdt_tests.py => test_pylibfdt.py} (97%)
>  create mode 100644 tox.ini
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2021-11-12  6:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12  4:16 [PATCH 0/6] More pylibfdt updates Rob Herring
     [not found] ` <20211112041633.741598-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-11-12  4:16   ` [PATCH 1/6] README: Update pylibfdt install instructions Rob Herring
2021-11-12  4:16   ` [PATCH 2/6] pylibfdt: Add packaging metadata Rob Herring
2021-11-12  4:16   ` [PATCH 3/6] pylibfdt_tests: Don't depend on built dtbs Rob Herring
     [not found]     ` <20211112041633.741598-4-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-11-12  4:57       ` David Gibson
2021-11-12  4:16   ` [PATCH 4/6] tests: rename pylibfdt_tests.py to test_pylibfdt.py Rob Herring
2021-11-12  4:16   ` [PATCH 5/6] pylibfdt: Include tests and test data in packaging Rob Herring
2021-11-12  4:16   ` [PATCH 6/6] pylibfdt: Add tox support Rob Herring
2021-11-12  6:10   ` David Gibson [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=YY4FabtkB6eis8QM@yekko \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).