From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Paul Burton <paul.burton@imgtec.com>, Wolfram Sang <wsa@the-dreams.de>
Cc: linux-mips@linux-mips.org, rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org
Subject: [rtc-linux] Re: [PATCH 16/28] rtc: m41t80: add devicetree probe support
Date: Mon, 30 Nov 2015 17:56:21 +0100 [thread overview]
Message-ID: <20151130165621.GG22136@piout.net> (raw)
In-Reply-To: <1448900513-20856-17-git-send-email-paul.burton@imgtec.com>
Hi,
On 30/11/2015 at 16:21:41 +0000, Paul Burton wrote :
> Allow the m41t80 RTC driver to be probed via devicetree.
>
This patch is probably unnecessary as "m41t81s" is already part of
m41t80_id[] and will be matched with "st,m41t81s" by the i2c core. See
http://lxr.free-electrons.com/source/drivers/i2c/i2c-core.c#L700
I actually don't know how to get people to stop submitting that kind of
patches :)
--
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.
next prev parent reply other threads:[~2015-11-30 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 16:21 [rtc-linux] [PATCH 00/28] MIPS Boston board support Paul Burton
2015-11-30 16:21 ` [rtc-linux] [PATCH 16/28] rtc: m41t80: add devicetree probe support Paul Burton
2015-11-30 16:56 ` Alexandre Belloni [this message]
2015-11-30 16:34 ` [rtc-linux] Re: [PATCH 00/28] MIPS Boston board support Mark Brown
2015-12-10 16:26 ` Linus Walleij
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=20151130165621.GG22136@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=rtc-linux@googlegroups.com \
--cc=wsa@the-dreams.de \
/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