public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Raghavendra Chandra Ganiga <ravi23ganiga@gmail.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
	a.zummo@towertech.it
Subject: Re: [PATCH] rtc: changed raw spi calls to register map calls
Date: Wed, 31 Aug 2016 22:21:18 +0530	[thread overview]
Message-ID: <57C70B06.7030207@gmail.com> (raw)
In-Reply-To: <20160830214837.4muxmee3mueimhg4@piout.net>



On Wednesday 31 August 2016 03:18 AM, Alexandre Belloni wrote:
> Hi,
> 
> Please fix the subject, this patch is ds1347 specific.
> 
Yes I will fix the subject

> On 31/08/2016 at 01:28:33 +0530, RAGHAVENDRA GANIGA wrote :
>> From 2ec82b6c9b99647e31d26c4c828dc7c51af8a633 Mon Sep 17 00:00:00 2001
>> From: Raghavendra Ganiga <ravi23ganiga@gmail.com>
>> Date: Wed, 31 Aug 2016 01:13:30 +0530
>> Subject: [PATCH] rtc: changed raw spi calls to register map calls
>>
>> This patch changes calls of spi read write calls to register map
>> read and write calls
>>
> 
> Can you explain why you need that change? I'm not sure what you gain
> from it (it makes the driver and the kernel bigger).
> 
Regmaps abstract layer are a better way of accessing register through 
spi interface rather than accessing directly through SPI layer

>>  	/* year in linux is from 1900 i.e in range of 100
>> -	in rtc it is from 00 to 99 */
>> +	 * in rtc it is from 00 to 99
>> +	 */
> 
> Unrelated change.
> 
> 
will have a seperate patch for this checkpatch.pl fix

      reply	other threads:[~2016-08-31 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 19:58 [PATCH] rtc: changed raw spi calls to register map calls RAGHAVENDRA GANIGA
2016-08-30 21:48 ` Alexandre Belloni
2016-08-31 16:51   ` Raghavendra Chandra Ganiga [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=57C70B06.7030207@gmail.com \
    --to=ravi23ganiga@gmail.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.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