From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexander Stein <alexander.stein@systec-electronic.com>,
linux-gpio@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH] gpio: Timestamp events in hardirq handler
Date: Tue, 23 Jan 2018 15:53:02 +0200 [thread overview]
Message-ID: <87lggolm0x.fsf@linux.intel.com> (raw)
In-Reply-To: <CACRpkdY2U1N+xHAKjxjAEzD-hMuDCveYuxOLNzyy=x8N+CiiLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hi,
Linus Walleij <linus.walleij@linaro.org> writes:
> On Tue, Jan 23, 2018 at 1:37 PM, Felipe Balbi
> <felipe.balbi@linux.intel.com> wrote:
>> Linus Walleij <linus.walleij@linaro.org> writes:
>>> On Thu, Nov 30, 2017 at 10:46 AM, Alexander Stein
>>> <alexander.stein@systec-electronic.com> wrote:
>>>> On Thursday, November 30, 2017, 10:26:55 AM CET Linus Walleij wrote:
>>>
>>>>> + s64 timestamp;
>>>> ^^^
>>>> u64? ktime_get_real_ns() returns u64 and struct gpioevent_data
>>>> has __u64 for timestamp.
>>>
>>> OK sorry, fixing it. Thanks for noticing!
>>
>> This is not on next. Will it miss this merge window?
>
> I realized yesterday when doing a security fix that it was missing.
>
> Because I didn't get the merge conflict I expected :D
>
> So I merged it. Don't worry. Sorry for the fuzz!
No problem, I'll refetch linux-next tomorrow or the day after and start
testing it.
Thanks
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-01-23 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 9:26 [PATCH] gpio: Timestamp events in hardirq handler Linus Walleij
2017-11-30 9:32 ` Felipe Balbi
2017-11-30 9:48 ` Linus Walleij
2017-11-30 9:46 ` Alexander Stein
2017-11-30 9:49 ` Linus Walleij
2018-01-23 12:37 ` Felipe Balbi
2018-01-23 13:42 ` Linus Walleij
2018-01-23 13:53 ` Felipe Balbi [this message]
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=87lggolm0x.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=alexander.stein@systec-electronic.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--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).