Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Hector Martin <marcan@marcan.st>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] alsaseq: fix constant objects in Python 3
Date: Mon, 10 Aug 2020 16:12:23 +0200	[thread overview]
Message-ID: <s5heeoe4mk8.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200805154243.64485-1-marcan@marcan.st>

On Wed, 05 Aug 2020 17:42:43 +0200,
Hector Martin wrote:
> 
> In Py3 everything is a long, so we can't get away with duplicating the
> integer object layout any more. Properly subclass PyLong_Type instead,
> with a bit of a hack to add an extra name field after the variable-sized
> data section.
> 
> Also get rid of the enum type stuff, which seems to be unused cruft, and
> the numprotocol stuff, because the base type can take care of that (and
> we can't map arbitrary arithmetic results back to constants anyway).
> 
> Signed-off-by: Hector Martin <marcan@marcan.st>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2020-08-10 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 15:42 [PATCH] alsaseq: fix constant objects in Python 3 Hector Martin
2020-08-10 14:12 ` Takashi Iwai [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=s5heeoe4mk8.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=marcan@marcan.st \
    /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