All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Igor Mammedov <imammedo@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	John Snow <jsnow@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Shiju Jose <shiju.jose@huawei.com>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/1] Sync kernel-doc.py with Linux upstream
Date: Tue, 6 Jan 2026 16:51:35 +0000	[thread overview]
Message-ID: <aV09l22pHEKP6ntp@redhat.com> (raw)
In-Reply-To: <cover.1767716928.git.mchehab+huawei@kernel.org>

On Tue, Jan 06, 2026 at 05:38:18PM +0100, Mauro Carvalho Chehab wrote:
> Hi Peter/John,
> 
> There were several updates at kernel-doc upstream fixing bugs,
> doing cleanups and a couple of improvements.
> 
> Better to keep QEMU in sync with such changes.
> 
> Worth mentioning that we did some changes on Linux at the
> kernel-doc.py script itself, to avoid Kernel build to crash
> with too old Python versions, as there docs build is a
> separate target, and python >= 3.6 is a new requirement
> there.
> 
> On kernel, if python < 3.6, it will simply ignore docs
> build (emitting a warning).
> 
> I opted to not backport such changes, but if you prefer
> doing that, I can do that on a v2.

QEMU mandates Python >= 3.9 (enforced by 'configure'), so there's no need
to worry about anything older than that.


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2026-01-06 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 16:38 [PATCH 0/1] Sync kernel-doc.py with Linux upstream Mauro Carvalho Chehab
2026-01-06 16:38 ` [PATCH 1/1] kernel-doc.py: sync with upstream Kernel v6.19-rc4 Mauro Carvalho Chehab
2026-01-20 12:55   ` Michael S. Tsirkin
2026-01-06 16:51 ` Daniel P. Berrangé [this message]
2026-01-13 11:44 ` [PATCH 0/1] Sync kernel-doc.py with Linux upstream Peter Maydell
2026-01-13 12:08   ` Daniel P. Berrangé
2026-01-13 13:04     ` Peter Maydell
2026-01-13 13:20       ` Daniel P. Berrangé
2026-01-13 19:52     ` John Snow
2026-01-13 20:04       ` Mauro Carvalho Chehab

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=aV09l22pHEKP6ntp@redhat.com \
    --to=berrange@redhat.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=imammedo@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shiju.jose@huawei.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 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.