[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201031000139.GA7042@sol>
Date: Sat, 31 Oct 2020 08:01:39 +0800
From: Kent Gibson <warthog618@...il.com>
To: Bartosz Golaszewski <bgolaszewski@...libre.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] gpiolib: cdev: allow edge event timestamps to be
configured as REALTIME
On Fri, Oct 30, 2020 at 03:52:24PM +0100, Bartosz Golaszewski wrote:
> On Fri, Oct 30, 2020 at 3:49 PM Bartosz Golaszewski
> <bgolaszewski@...libre.com> wrote:
> >
> > On Thu, Oct 29, 2020 at 12:22 AM Kent Gibson <warthog618@...il.com> wrote:
> > >
> > > On Wed, Oct 28, 2020 at 05:01:49PM +0100, Linus Walleij wrote:
> > > > On Thu, Oct 15, 2020 at 1:12 AM Kent Gibson <warthog618@...il.com> wrote:
> > > >
> > > > > This patch set adds the option to select CLOCK_REALTIME as the source
> > > > > clock for line events.
> > > > >
> > > > > The first patch is the core of the change, while the remaining two update
> > > > > the GPIO tools to make use of the new option.
> > > > >
> > > > > Changes for v2:
> > > > > - change line_event_timestamp() return to u64 to avoid clipping to 32bits
> > > > > on 32bit platforms.
> > > > > - fix the line spacing after line_event_timestamp()
> > > >
> > > > Where are we standing with this patch set? Good to go so
> > > > I should just try to merge it?
> > > >
> > >
> > > I'm fine with it, especially now that I've tested it on 32bit platforms
> > > as well as 64bit.
> > >
> > > Bart was ok with v1, and I doubt the changes for v2 would negatively
> > > impact that, though I did overlook adding his review tag.
> > >
> > > Cheers,
> > > Kent.
> > >
> > > > Yours,
> > > > Linus Walleij
> >
> > I'll take it through my tree then.
> >
> > Bartosz
>
> 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??
Specifically it is based over/conflicts with:
2cc522d3931b gpio: uapi: kernel-doc formatting improvements
If I rebase it onto devel then you will get a conflict when those merge.
Is that what you want?
Cheers,
Kent.
Powered by blists - more mailing lists