From: Linus Walleij <linus.walleij@linaro.org>
To: Kent Gibson <warthog618@gmail.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] gpiolib: cdev: allow edge event timestamps to be configured as REALTIME
Date: Fri, 6 Nov 2020 14:49:12 +0100 [thread overview]
Message-ID: <CACRpkdZ2MoV04YCVxCxG-wPTgNAORkN6D+AXVOC1vEqsdGqo8w@mail.gmail.com> (raw)
In-Reply-To: <20201031000139.GA7042@sol>
On Sat, Oct 31, 2020 at 1:01 AM Kent Gibson <warthog618@gmail.com> wrote:
> On Fri, Oct 30, 2020 at 03:52:24PM +0100, Bartosz Golaszewski wrote:
> > The series no longer applies on top of v5.10-rc1. Could you rebase and resend?
>
> Nuts, it relies on my doc tidy-up series that Linus has pulled into
> fixes, and so will likely go into v5.10-rc2??
If I have time to get the GPIO fixes into -rc2. Otherwise -rc3
and then I need to merge the resulting -rc into the devel branch
before applying.
I will get to it sooner or later, I think Bartosz might have some
more GPIO fixes that I need to pull first before sending any
fixes upstream.
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-11-06 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 23:11 [PATCH v2 0/3] gpiolib: cdev: allow edge event timestamps to be configured as REALTIME Kent Gibson
2020-10-14 23:11 ` [PATCH v2 1/3] " Kent Gibson
2020-10-16 14:13 ` Andy Shevchenko
2020-10-16 23:27 ` Kent Gibson
2020-10-14 23:11 ` [PATCH v2 2/3] tools: gpio: add support for reporting realtime event clock to lsgpio Kent Gibson
2020-10-14 23:11 ` [PATCH v2 3/3] tools: gpio: add option to report wall-clock time to gpio-event-mon Kent Gibson
2020-10-28 16:01 ` [PATCH v2 0/3] gpiolib: cdev: allow edge event timestamps to be configured as REALTIME Linus Walleij
2020-10-28 23:22 ` Kent Gibson
2020-10-30 14:49 ` Bartosz Golaszewski
2020-10-30 14:52 ` Bartosz Golaszewski
2020-10-31 0:01 ` Kent Gibson
2020-11-02 8:56 ` Bartosz Golaszewski
2020-11-06 13:49 ` Linus Walleij [this message]
2020-12-01 18:20 ` Bartosz Golaszewski
2020-12-05 22:23 ` Linus Walleij
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=CACRpkdZ2MoV04YCVxCxG-wPTgNAORkN6D+AXVOC1vEqsdGqo8w@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@gmail.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;
as well as URLs for NNTP newsgroup(s).