From: Miquel Raynal <miquel.raynal@bootlin.com>
To: kernel test robot <lkp@intel.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
kbuild-all@lists.01.org, linux-rtc@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Gareth Williams <gareth.williams.jx@renesas.com>,
Milan Stevanovic <milan.stevanovic@se.com>,
Jimmy Lalande <jimmy.lalande@se.com>,
Pascal Eberhard <pascal.eberhard@se.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Clement Leger <clement.leger@bootlin.com>,
Michel Pollet <michel.pollet@bp.renesas.com>
Subject: Re: [PATCH v4 2/5] rtc: rzn1: Add new RTC driver
Date: Tue, 10 May 2022 09:29:11 +0200 [thread overview]
Message-ID: <20220510092911.5ab2f15a@xps13> (raw)
In-Reply-To: <202205100552.VY3kCkh5-lkp@intel.com>
Hi Alex,
lkp@intel.com wrote on Tue, 10 May 2022 05:26:55 +0800:
> Hi Miquel,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on abelloni/rtc-next]
> [also build test ERROR on robh/for-next linus/master v5.18-rc6 next-20220509]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch]
>
[...]
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> >> drivers/rtc/rtc-rzn1.c:23:10: fatal error: linux/soc/renesas/r9a06g032-sysctrl.h: No such file or directory
> 23 | #include <linux/soc/renesas/r9a06g032-sysctrl.h>
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
That include is no longer needed in this driver (and should be merged
through another tree). Tell me if I need to resend or if you can fix it
while applying.
Thanks,
Miquèl
next prev parent reply other threads:[~2022-05-10 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 15:45 [PATCH v4 0/5] RZ/N1 RTC support Miquel Raynal
2022-05-09 15:45 ` [PATCH v4 1/5] dt-bindings: rtc: rzn1: Describe the RZN1 RTC Miquel Raynal
2022-05-09 15:45 ` [PATCH v4 2/5] rtc: rzn1: Add new RTC driver Miquel Raynal
2022-05-09 21:26 ` kernel test robot
2022-05-10 7:29 ` Miquel Raynal [this message]
2022-05-10 10:06 ` Krzysztof Kozlowski
2022-05-12 7:27 ` Miquel Raynal
2022-05-10 11:40 ` kernel test robot
2022-05-09 15:45 ` [PATCH v4 3/5] rtc: rzn1: Add alarm support Miquel Raynal
2022-05-09 15:45 ` [PATCH v4 4/5] rtc: rzn1: Add oscillator offset support Miquel Raynal
2022-05-09 15:45 ` [PATCH v4 5/5] MAINTAINERS: Add myself as maintainer of the RZN1 RTC driver Miquel Raynal
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=20220510092911.5ab2f15a@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=clement.leger@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=gareth.williams.jx@renesas.com \
--cc=geert+renesas@glider.be \
--cc=herve.codina@bootlin.com \
--cc=jimmy.lalande@se.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=magnus.damm@gmail.com \
--cc=michel.pollet@bp.renesas.com \
--cc=milan.stevanovic@se.com \
--cc=pascal.eberhard@se.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).