From: Jack Winch <sunt.un.morcov@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Helmut Grohne <helmut.grohne@intenta.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bartekgola@gmail.com>
Subject: Re: [libgpiod] cxx bindings: time_point vs duration
Date: Thu, 22 Oct 2020 12:47:14 +0300 [thread overview]
Message-ID: <CAFhCfDb9pbPMAj-7zqVWWMfprnFQEaozx-CV7VP25kP437diCw@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=Mfs7CSS_3BU6geAyDq0bNA9Q6eQvw_-iJCttGKimbZHjg@mail.gmail.com>
> Jack: FYI the clock configuration didn't make it this merge window so
> it'll be released in v5.11.
Ah, that is a shame. Such is life, though.
> I also don't envision making a libgpiod
> v2.0 release any earlier than that so we have plenty of time to
> discuss it and come to the right conclusion.
That is also a shame, but at least that gives some time to undertake
further review of libgpiod v2.0 and potentially make some further
improvements. What's the time window for this?
Jack
On Thu, Oct 22, 2020 at 12:36 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> On Thu, Oct 22, 2020 at 11:09 AM Jack Winch <sunt.un.morcov@gmail.com> wrote:
> >
>
> [snip]
>
> > What I did not want to see happen is the change as currently proposed
> > be applied and cause issues in the future.
> >
>
> Jack: FYI the clock configuration didn't make it this merge window so
> it'll be released in v5.11. I also don't envision making a libgpiod
> v2.0 release any earlier than that so we have plenty of time to
> discuss it and come to the right conclusion.
>
> Bartosz
>
> [snip]
next prev parent reply other threads:[~2020-10-22 9:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 8:38 [libgpiod] cxx bindings: time_point vs duration Helmut Grohne
2020-10-15 9:26 ` Bartosz Golaszewski
2020-10-15 9:35 ` Helmut Grohne
2020-10-15 10:05 ` Bartosz Golaszewski
2020-10-15 10:57 ` Helmut Grohne
2020-10-15 11:43 ` Bartosz Golaszewski
2020-10-15 12:13 ` Helmut Grohne
2020-10-15 12:16 ` Bartosz Golaszewski
2020-10-21 13:57 ` Jack Winch
2020-10-21 14:35 ` Jack Winch
2020-10-21 15:14 ` Bartosz Golaszewski
2020-10-21 15:44 ` Jack Winch
2020-10-22 6:39 ` Helmut Grohne
2020-10-22 9:09 ` Jack Winch
2020-10-22 9:35 ` Bartosz Golaszewski
2020-10-22 9:47 ` Jack Winch [this message]
2020-10-22 11:55 ` Bartosz Golaszewski
2020-10-22 12:22 ` Jack Winch
2020-10-23 16:22 ` 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=CAFhCfDb9pbPMAj-7zqVWWMfprnFQEaozx-CV7VP25kP437diCw@mail.gmail.com \
--to=sunt.un.morcov@gmail.com \
--cc=bartekgola@gmail.com \
--cc=brgl@bgdev.pl \
--cc=helmut.grohne@intenta.de \
--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 NNTP newsgroup(s).