From: Michael Olbrich <m.olbrich@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [APPLIED] libpwm: version bump 1.0-rc1 -> 1.0-rc2
Date: Tue, 5 Aug 2025 08:33:29 +0200 [thread overview]
Message-ID: <20250805063329.GD1233356@pengutronix.de> (raw)
In-Reply-To: <xqrgpviblzlfz5cbikfjomq5hghh2ebkv7euxpn7xbd4b5q6my@swcdzqjkisdf>
On Tue, Aug 05, 2025 at 08:09:05AM +0200, Uwe Kleine-König wrote:
> Hello Michael,
>
> On Tue, Aug 05, 2025 at 06:59:47AM +0200, Michael Olbrich wrote:
> > Thanks, applied as dee8d80ab1e9d272f94348fe3aaffdf57163c6c7.
> >
> > Michael
> >
> > [sent from post-receive hook]
> >
> > On Tue, 05 Aug 2025 06:59:47 +0200, Uwe Kleine-König <u.kleine-koenig@baylibre.com> wrote:
> > > The rc2 release contains a few minor bug fixes and ships a copy of
> > > <linux/pwm.h> which makes it possible to compile in the character device
> > > support with kernel headers older than 6.17-rc1.
> > >
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
> > > Message-Id: <20250729172757.164306-2-u.kleine-koenig@baylibre.com>
> > > Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> > >
> > > diff --git a/rules/libpwm.make b/rules/libpwm.make
> > > index 4c14e030d6e2..82770805f341 100644
> > > --- a/rules/libpwm.make
> > > +++ b/rules/libpwm.make
> > > @@ -14,11 +14,11 @@ PACKAGES-$(PTXCONF_LIBPWM) += libpwm
> > > #
> > > # Paths and names
> > > #
> > > -LIBPWM_VERSION := 1.0-rc1
> > > -LIBPWM_MD5 := bb8032cd03c25a0dcdc76712acda714c
> > > +LIBPWM_VERSION := 1.0-rc2
> > > +LIBPWM_MD5 := ccf05e263bd26418311e0e93848b3a71
> > > LIBPWM := libpwm-$(LIBPWM_VERSION)
> > > LIBPWM_SUFFIX := tar.xz
> > > -LIBPWM_URL := https://mirrors.edge.kernel.org/pub/linux/kernel/people/ukleinek/libpwm/libpwm-1.0-rc1.tar.xz
> > > +LIBPWM_URL := https://mirrors.edge.kernel.org/pub/linux/kernel/people/ukleinek/libpwm/libpwm-$(LIBPWM_VERSION).tar.xz
> > > LIBPWM_SOURCE := $(SRCDIR)/$(LIBPWM).$(LIBPWM_SUFFIX)
> > > LIBPWM_DIR := $(BUILDDIR)/$(LIBPWM)
> > > LIBPWM_BUILD_OOT := YES
>
> Hmm, it seems you didn't like my v2[1], but I thought you didn't like my
> v1 either ... 🤔
Sorry about that. Looks like I queued v1 just before you sent v2 (otherwise
b4 would have picked up v2 instead). And I forgot about my own comments...
And I didn't see the new version before now.
I've queued v2 as well now (which is just the kernel header stuff) with a
modified commit message. Should hit master soon.
Michael
> Best regards
> Uwe
>
> [1] https://lore.ptxdist.org/ptxdist/20250801104042.177835-2-u.kleine-koenig@baylibre.com/
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-08-05 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 17:27 [ptxdist] [PATCH] " Uwe Kleine-König
2025-08-01 9:36 ` Michael Olbrich
2025-08-05 4:59 ` [ptxdist] [APPLIED] " Michael Olbrich
2025-08-05 6:09 ` Uwe Kleine-König
2025-08-05 6:33 ` Michael Olbrich [this message]
2025-08-05 14:12 ` Uwe Kleine-König
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=20250805063329.GD1233356@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=u.kleine-koenig@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox