From: Sekhar Nori <nsekhar@ti.com>
To: Keerthy <j-keerthy@ti.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
<linux-rtc@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Linux OMAP List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] rtc: omap: Support scratch registers
Date: Mon, 6 Nov 2017 12:32:22 +0530 [thread overview]
Message-ID: <764e60e1-59a4-1082-4307-9d9742d86562@ti.com> (raw)
In-Reply-To: <4741d4c7-d6f7-ecdb-1eed-1293175f38d9@ti.com>
On Monday 06 November 2017 12:29 PM, Keerthy wrote:
>
>
> On Monday 06 November 2017 12:25 PM, Sekhar Nori wrote:
>> + linux omap list
>>
>> On Tuesday 31 October 2017 09:57 PM, Alexandre Belloni wrote:
>>> Register an nvmem device to expose the 3 scratch registers (total of 12
>>> bytes) to both userspace and kernel space.
>>>
>>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>
>> Looks good to me.
>>
>> Reviewed-by: Sekhar Nori <nsekhar@ti.com>
>>
>> Curious on what you are using these registers for.
>
> This is in response to this:
> https://patchwork.kernel.org/patch/9684955/
Ah, okay. Makes sense then :)
Regards,
Sekhar
next prev parent reply other threads:[~2017-11-06 7:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 16:27 [PATCH] rtc: omap: Support scratch registers Alexandre Belloni
2017-11-06 6:55 ` Sekhar Nori
2017-11-06 6:59 ` Keerthy
2017-11-06 7:02 ` Sekhar Nori [this message]
2017-11-08 6:00 ` Keerthy
2017-11-08 6:27 ` Alexandre Belloni
2017-11-08 7:08 ` Keerthy
2017-11-08 7:16 ` Alexandre Belloni
2017-11-08 8:06 ` Keerthy
2017-11-08 8:21 ` Alexandre Belloni
2017-11-08 8:31 ` Keerthy
2017-11-08 8:32 ` Keerthy
2017-11-08 8:35 ` Alexandre Belloni
2017-11-08 8:48 ` Keerthy
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=764e60e1-59a4-1082-4307-9d9742d86562@ti.com \
--to=nsekhar@ti.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rtc@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).