From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [rtc-linux] Re: [PATCH 5/5] rtc: v3020: move rtc-v3020.h to platform_data
Date: Sat, 9 Jul 2016 10:25:40 +0200 [thread overview]
Message-ID: <20160709082540.GO22202@piout.net> (raw)
In-Reply-To: <87bn2745lb.fsf@belgarion.home>
On 09/07/2016 at 09:45:52 +0200, Robert Jarzmik wrote :
> Alexandre Belloni <alexandre.belloni@free-electrons.com> writes:
>
> > rtc-v3020.h belongs to include/linux/platform_data/
> >
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> > ---
> > Cc: Daniel Mack <daniel@zonque.org>
> > Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
> > Cc: Robert Jarzmik <robert.jarzmik@free.fr>
> > Cc: linux-arm-kernel@lists.infradead.org
> > arch/arm/mach-pxa/cm-x270.c | 2 +-
> > arch/arm/mach-pxa/cm-x300.c | 2 +-
> > arch/arm/mach-pxa/em-x270.c | 2 +-
> > drivers/rtc/rtc-v3020.c | 2 +-
> > include/linux/{ => platform_data}/rtc-v3020.h | 0
> > 5 files changed, 4 insertions(+), 4 deletions(-)
> > rename include/linux/{ => platform_data}/rtc-v3020.h (100%)
> For mach-pxa :
> Acked-by: Robert Jarzmik <robert.jarzmik@free.fr>
>
> Is this going through your rtc tree, or should I pick it up through the pxa one ?
>
Actually, I've pushed it through rtc-next yesterday. I've just added
your ack now.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel 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.
prev parent reply other threads:[~2016-07-09 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 22:02 [rtc-linux] [PATCH 1/5] rtc: ds17287: remove unused header Alexandre Belloni
2016-06-26 22:03 ` [rtc-linux] [PATCH 2/5] rtc: ds1286: move header to linux/rtc Alexandre Belloni
2016-06-26 22:03 ` [rtc-linux] [PATCH 3/5] rtc: ds2404: move rtc-ds2404.h to platform_data Alexandre Belloni
2016-06-26 22:03 ` [rtc-linux] [PATCH 4/5] rtc: m48t86: move m48t86.h " Alexandre Belloni
2016-06-27 6:49 ` [rtc-linux] " Alexander Clouter
2016-06-27 16:00 ` [rtc-linux] " Hartley Sweeten
2016-06-27 16:12 ` [rtc-linux] " Jason Cooper
2016-06-26 22:03 ` [rtc-linux] [PATCH 5/5] rtc: v3020: move rtc-v3020.h " Alexandre Belloni
2016-07-09 7:45 ` [rtc-linux] " Robert Jarzmik
2016-07-09 8:25 ` 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=20160709082540.GO22202@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--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