From: Michael Riesch <michael.riesch@wolfvision.net>
To: ptxdist@pengutronix.de
Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Michael Riesch <michael.riesch@wolfvision.net>
Subject: [ptxdist] [PATCH v2 0/2] libcamera: version bump 0.0.5 -> 0.2.0
Date: Wed, 15 May 2024 09:04:22 +0200 [thread overview]
Message-ID: <20240515-feature-libcamera-0-2-0-v2-0-47555e12eedd@wolfvision.net> (raw)
Habidere,
This series features a long overdue libcamera version bump to v0.2.0
along a pipewire version bump that is required due to an API breakage.
Just in time before libcamera v0.3.0 will be released, right, Kieran? ;-)
Looking forward to your comments!
---
Changes in v2:
- drop already accepted patch that fixes the libcamera tarball repo
- enable udev/hotplug configuration option explicitly
- Link to v1: https://lore.kernel.org/r/20240305-feature-libcamera-0-2-0-v1-0-0625f2fd9dc6@wolfvision.net
---
Michael Riesch (2):
libcamera: version bump 0.0.5 -> 0.2.0
pipewire: version bump 1.0.1 -> 1.0.3
rules/libcamera.make | 5 +++--
rules/pipewire.make | 4 ++--
2 files changed, 5 insertions(+), 4 deletions(-)
---
base-commit: 9de477ba07b1778daa58537121091d9f3b8ea670
change-id: 20240305-feature-libcamera-0-2-0-5cc0ab00b499
Best regards,
--
Michael Riesch <michael.riesch@wolfvision.net>
next reply other threads:[~2024-05-15 7:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 7:04 Michael Riesch [this message]
2024-05-15 7:04 ` [ptxdist] [PATCH v2 1/2] " Michael Riesch
2024-05-15 10:04 ` Michael Tretter
2024-05-21 9:58 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-05-15 7:04 ` [ptxdist] [PATCH v2 2/2] pipewire: version bump 1.0.1 -> 1.0.3 Michael Riesch
2024-05-15 10:05 ` Michael Tretter
2024-05-21 9:58 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20240515-feature-libcamera-0-2-0-v2-0-47555e12eedd@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=kieran.bingham@ideasonboard.com \
--cc=ptxdist@pengutronix.de \
/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