From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Keguang Zhang <keguang.zhang@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] watchdog: Enable COMPILE_TEST for more drivers
Date: Fri, 4 Aug 2023 11:23:29 -0600 [thread overview]
Message-ID: <CAL_JsqJip=r-xObhCOnL0sue67Pems8wO1FP3x=rCGXARCA1sw@mail.gmail.com> (raw)
In-Reply-To: <20230729-twerp-avert-70577ff7d952@spud>
On Sat, Jul 29, 2023 at 4:22 AM Conor Dooley <conor@kernel.org> wrote:
>
> On Fri, Jul 28, 2023 at 01:50:21PM -0600, Rob Herring wrote:
> > There's quite a few watchdog drivers which are easily enabled for
> > COMPILE_TEST, so let's enable them.
> >
> > Signed-off-by: Rob Herring <robh@kernel.org>
> > ---
> > Passed allyesconfig builds on arm, arm64, x86, riscv, powerpc, sparc
>
> Doing its job I suppose, the riscv patchwork automation stuff has
> spotted one new complaint for allmodconfig:
> stm32_iwdg.c:77:19: warning: unused function 'reg_read' [-Wunused-function]
Looks like that's a clang W=1 warning only. Presumably it was already
there before this patch with the right config.
Rob
prev parent reply other threads:[~2023-08-04 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 19:50 [PATCH] watchdog: Enable COMPILE_TEST for more drivers Rob Herring
2023-07-28 20:50 ` Guenter Roeck
2023-07-29 10:22 ` Conor Dooley
2023-08-04 17:23 ` Rob Herring [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='CAL_JsqJip=r-xObhCOnL0sue67Pems8wO1FP3x=rCGXARCA1sw@mail.gmail.com' \
--to=robh@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=keguang.zhang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=wim@linux-watchdog.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).