All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wilfred Mallawa <wilfred.mallawa@wdc.com>
To: "jsnow@redhat.com" <jsnow@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "hreitz@redhat.com" <hreitz@redhat.com>,
	"kwolf@redhat.com" <kwolf@redhat.com>,
	"bleal@redhat.com" <bleal@redhat.com>,
	"crosa@redhat.com" <crosa@redhat.com>,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Subject: Re: [PATCH 0/3] python: testing fixes
Date: Sun, 4 Dec 2022 22:38:34 +0000	[thread overview]
Message-ID: <42bbc7e8420283f834cff7e3df362ba98c5d7346.camel@wdc.com> (raw)
In-Reply-To: <20221203005234.620788-1-jsnow@redhat.com>

On Fri, 2022-12-02 at 19:52 -0500, John Snow wrote:
> A few tiny touchups needed for cutting edge 'flake8' tooling, a minor
> type touchup in iotests, and extending the python tests to cover the
> recently released Python 3.11.
> 
> John Snow (3):
>   Python: fix flake8 config
>   iotests/check: Fix typing for sys.exit() value
>   python: add 3.11 to supported list
> 
>  python/setup.cfg         | 6 ++++--
>  tests/qemu-iotests/check | 2 +-
>  2 files changed, 5 insertions(+), 3 deletions(-)
> 
> -- 
> 2.38.1
> 
I see you've left Westeros! xD

Reviewed-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
> 
> 


  parent reply	other threads:[~2022-12-04 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03  0:52 [PATCH 0/3] python: testing fixes John Snow
2022-12-03  0:52 ` [PATCH 1/3] Python: fix flake8 config John Snow
2022-12-03  0:52 ` [PATCH 2/3] iotests/check: Fix typing for sys.exit() value John Snow
2022-12-03  0:52 ` [PATCH 3/3] python: add 3.11 to supported list John Snow
2022-12-04 22:38 ` Wilfred Mallawa [this message]
2023-01-04 22:25   ` [PATCH 0/3] python: testing fixes John Snow

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=42bbc7e8420283f834cff7e3df362ba98c5d7346.camel@wdc.com \
    --to=wilfred.mallawa@wdc.com \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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 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.