From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
Cc: a.zummo@towertech.it, linux-rtc@vger.kernel.org,
val.krutov@erd.epson.com
Subject: Re: [PATCH] rtc: rx6110: Remove useless rx6110_remove
Date: Fri, 15 Nov 2019 12:00:56 +0100 [thread overview]
Message-ID: <20191115110056.GN3572@piout.net> (raw)
In-Reply-To: <20191108002113.14791-1-iwamatsu@nigauri.org>
On 08/11/2019 09:21:13+0900, Nobuhiro Iwamatsu wrote:
> rx6110_remove is empty, remove it.
>
> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
> ---
> drivers/rtc/rtc-rx6110.c | 6 ------
> 1 file changed, 6 deletions(-)
>
Applied, thanks.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-11-15 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 0:21 [PATCH] rtc: rx6110: Remove useless rx6110_remove Nobuhiro Iwamatsu
2019-11-15 11:00 ` 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=20191115110056.GN3572@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=iwamatsu@nigauri.org \
--cc=linux-rtc@vger.kernel.org \
--cc=val.krutov@erd.epson.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;
as well as URLs for NNTP newsgroup(s).