Linux RTC
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Harald Geyer <harald@ccbib.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
	Wim Van Sebroeck <wim@iguana.be>,
	rtc-linux@googlegroups.com, linux-watchdog@vger.kernel.org,
	kernel@pengutronix.de
Subject: [rtc-linux] Re: [PATCH 1/2] rtc: stmp3xxx: unify register access macros
Date: Sat, 3 Oct 2015 17:57:09 +0200	[thread overview]
Message-ID: <20151003155709.GE2694@piout.net> (raw)
In-Reply-To: <1443817082-24370-1-git-send-email-harald@ccbib.org>

On 02/10/2015 at 20:18:01 +0000, Harald Geyer wrote :
> Use STMP_OFFSET_REG_(SET|CLR) instead of defining _SET and _CLR for
> STMP3XXX_RTC_CTRL and STMP3XXX_RTC_PERSISTENT0 - no functional changes.
> 
> Signed-off-by: Harald Geyer <harald@ccbib.org>
> ---
>  drivers/rtc/rtc-stmp3xxx.c |   27 +++++++++++++--------------
>  1 file changed, 13 insertions(+), 14 deletions(-)
> 
Applied, thanks.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

-- 
-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

      parent reply	other threads:[~2015-10-03 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 20:18 [rtc-linux] [PATCH 1/2] rtc: stmp3xxx: unify register access macros Harald Geyer
2015-10-02 20:18 ` [rtc-linux] [PATCH 2/2] watchdog: stmp3xxx: Implement GETBOOTSTATUS Harald Geyer
2015-10-03 16:47   ` [rtc-linux] " Alexandre Belloni
2015-10-03 15:57 ` Alexandre Belloni [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=20151003155709.GE2694@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=a.zummo@towertech.it \
    --cc=harald@ccbib.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=wim@iguana.be \
    /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