From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: glasveze@delta.nl, linux-rtc@vger.kernel.org, devicetree@vger.kernel.org
Cc: a.zummo@towertech.it, alexandre.belloni@bootlin.com,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
Mike Looijmans <mike.looijmans@topic.nl>
Subject: Re: [PATCH 1/2] dt-bindings: rtc: ds1307: Add support for Epson RX8111
Date: Fri, 28 Oct 2022 13:38:20 -0400 [thread overview]
Message-ID: <fd226c82-ee6e-ce5b-3949-faaf88ded3b6@linaro.org> (raw)
In-Reply-To: <20221028144041.11067-1-glasveze@delta.nl>
On 28/10/2022 10:40, glasveze@delta.nl wrote:
> From: Mike Looijmans <mike.looijmans@topic.nl>
>
> The rx_8111 is quite similar to the rx_8030. This adds support for this
> chip to the ds1307 driver.
>
> This adds the entry to the devicetree bindings.
>
> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-28 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 14:40 [PATCH 1/2] dt-bindings: rtc: ds1307: Add support for Epson RX8111 glasveze
2022-10-28 14:40 ` [PATCH 2/2] " glasveze
2022-11-14 22:17 ` Alexandre Belloni
2022-10-28 17:38 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-31 6:54 [PATCH 1/2] dt-bindings: " glasveze
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.9ece6833-e74a-4c7a-a461-cb644d735850@emailsignatures365.codetwo.com>
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.0d2bd5fa-15cc-4b27-b94e-83614f9e5b38.26ae0640-23b6-42bd-b752-f9965c8a2c94@emailsignatures365.codetwo.com>
2022-10-31 7:09 ` Mike Looijmans
2022-10-28 14:19 glasveze
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=fd226c82-ee6e-ce5b-3949-faaf88ded3b6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=glasveze@delta.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=robh+dt@kernel.org \
/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).