From: Vincent Fazio <vfazio@xes-inc.com>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: RE: [libgpiod][PATCH] Revert "bindings: python: replace PyModule_AddObjectRef() with PyModule_AddObject()"
Date: Mon, 30 Mar 2026 13:34:14 +0000 [thread overview]
Message-ID: <PH1P110MB1603DF3349C616940C07CC6E9F52A@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20260330125023.109789-1-bartosz.golaszewski@oss.qualcomm.com>
> -----Original Message-----
> From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
> Sent: Monday, March 30, 2026 7:50 AM
> To: Linus Walleij <linusw@kernel.org>; Bartosz Golaszewski <brgl@kernel.org>;
> Vincent Fazio <vfazio@xes-inc.com>
> Cc: linux-gpio@vger.kernel.org; Bartosz Golaszewski
> <bartosz.golaszewski@oss.qualcomm.com>
> Subject: [libgpiod][PATCH] Revert "bindings: python: replace
> PyModule_AddObjectRef() with PyModule_AddObject()"
>
> This reverts commit b436d05809b17ed734d08a36a8913eb687506433.
>
> Commit 950ff3d1b300 ("bindings: python: drop python 3.9 support")
> removed support for python v3.9 and with v3.10 now being the minimum
> required version, we're now free to use PyModule_AddObjectRef().
>
> Signed-off-by: Bartosz Golaszewski
> <bartosz.golaszewski@oss.qualcomm.com>
Reviewed-by: Vincent Fazio <vfazio@xes-inc.com>
next prev parent reply other threads:[~2026-03-30 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 12:50 [libgpiod][PATCH] Revert "bindings: python: replace PyModule_AddObjectRef() with PyModule_AddObject()" Bartosz Golaszewski
2026-03-30 13:34 ` Vincent Fazio [this message]
2026-03-31 13:04 ` Bartosz Golaszewski
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=PH1P110MB1603DF3349C616940C07CC6E9F52A@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM \
--to=vfazio@xes-inc.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.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).